[tor-bugs] #27110 [Applications/Tor Browser]: TBB segfaults on I/O error and silently fails to restart

[Tor Bug Tracker & Wiki]

#27110: TBB segfaults on I/O error and silently fails to restart
--------------------------------------+-----------------------------------
 Reporter:  traumschule               |          Owner:  tbb-team
     Type:  defect                    |         Status:  needs_information
 Priority:  Medium                    |      Milestone:
Component:  Applications/Tor Browser  |        Version:
 Severity:  Normal                    |     Resolution:
 Keywords:                            |  Actual Points:
Parent ID:                            |         Points:
 Reviewer:                            |        Sponsor:
--------------------------------------+-----------------------------------

Comment (by traumschule):

 short update, this is all I could get so far:
 {{{
 $ ./firefox --version
 Mozilla Firefox 63.0a1
 ./firefox --debug
 ExceptionHandler::GenerateDump cloned child 3022
 ExceptionHandler::SendContinueSignalToChild sent continue signal to child
 ExceptionHandler::WaitForContinueSignal waiting for continue signal...
 [Child 2138, Chrome_ChildThread] WARNING: pipe error (3): Connection reset
 by peer: file
 /builds/worker/workspace/build/src/ipc/chromium/src/chrome/common/ipc_channel_posix.cc,
 line 356
 Bus error
 }}}

 Looking into ways to [https://unix.stackexchange.com/questions/77492
 /special-file-that-causes-i-o-error/144200#144200 simulate disk errors],
 like dm-flakey and
 [https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/tree/misc/e2fuzz.sh
 e2fuzz] to avoid kernel panics and get the fs flagged as unclean. Firejail
 is another option.

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