[tbb-bugs] #20100 [Applications/Tor Browser]: persistent libxul.so bug crashing TBB Linux/64 (but probably a bug in locally linked shared object)

[Tor Bug Tracker & Wiki]

#20100: persistent libxul.so bug crashing TBB Linux/64 (but probably a bug in
locally linked shared object)
--------------------------------------+-----------------------------------
 Reporter:  sjamaan                   |          Owner:  tbb-team
     Type:  defect                    |         Status:  needs_information
 Priority:  High                      |      Milestone:
Component:  Applications/Tor Browser  |        Version:
 Severity:  Major                     |     Resolution:
 Keywords:  tbb-crash                 |  Actual Points:
Parent ID:                            |         Points:
 Reviewer:                            |        Sponsor:
--------------------------------------+-----------------------------------

Comment (by ronvandaal_):

 Replying to [comment:10 gk]:
 > Following up on comment:2 would still be helpful.

 Will do that but problem occurs at random. Goes well for months, then
 suddenly a 2 crashes, a week no issues, another crash, etc. Will setup a
 new environment and let it run in gdb if it doesn't slow down the user
 experience.

 Besides that I wonder what your thoughts are on adding a hash check at the
 Bundles startup script? Libxul.so is quite vast with alot of shared
 library dependencies. I can't belief there isn't any kind of integrity
 checking done on this in Tor Browser Bundle. Bugs like these go under the
 radar, how many users would unpack the TBB bundle and notice a 1 byte
 change from a CALLQ to a JMPQ which basically has the same functionality
 and doesn't crash until further exploitation. It's still a wild guess why
 this happens, but integrity checking the binaries seems common sense.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20100#comment:11>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online