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

2018-09-15 Thread 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):

 reported it upstream: https://bugzilla.mozilla.org/show_bug.cgi?id=1491537

 Hit {{{segfault at 0 ip af1f6ca7 sp ae9a6080 error 6 in
 libxul.so[aed4b000+6b9e000]}}} once more, this time reloading trac:

 {{{
 JavaScript error:
 
http://ea5faa5po25cf7fb.onion/projects/tor/chrome/autocomplete/js/autocomplete.js,
 line 96: TypeError: $.browser is undefined
 ASSERT: Giving up waiting for the tab closing animation to finish (bug
 608589)
 ./Browser/start-tor-browser: line 375: 19262 Segmentation fault
 TOR_CONTROL_PASSWD=${TOR_CONTROL_PASSWD}
 ./firefox --class "Tor Browser" -profile
 TorBrowser/Data/Browser/profile.default "${@}" < /dev/null
 }}}

 syslog showed
 {{{
 Sep 15 10:37:45 t43 kernel: [1075156.616000] Chrome_~dThread[19315]:
 segfault at 0 ip af20d0a7 sp ae9b9080 error 6 in
 libxul.so[aed61000+6bb]
 Sep 15 10:37:46 t43 kernel: [1075157.839491] Chrome_~dThread[19578]:
 segfault at 0 ip af1940a7 sp ae940080 error 6 in
 libxul.so[aece8000+6bb]
 Sep 15 10:37:46 t43 kernel: [1075159.792345] Chrome_~dThread[19538]:
 segfault at 0 ip af24a0a7 sp ae9f6080 error 6 in
 libxul.so[aed9e000+6bb]
 Sep 15 10:37:52 t43 kernel: [1075166.289269] Chrome_~dThread[19559]:
 segfault at 0 ip af20e0a7 sp ae9ba080 error 6 in
 libxul.so[aed62000+6bb]
 }}}

 dpkg upgraded libc and other packages shortly before, wonder if this is
 related. dpkg.log:
 {{{
 2018-09-15 09:47:10 upgrade emacsen-common:all 3.0.2 3.0.3
 2018-09-15 10:01:39 upgrade gir1.2-gtksource-3.0:i386 3.24.8-1 3.24.9-1
 2018-09-15 10:08:40 upgrade gnome-settings-daemon:i386 3.28.1-1 3.30.0-1
 2018-09-15 10:12:57 upgrade libarchive-zip-perl:all 1.63-1 1.64-1
 2018-09-15 10:17:59 upgrade libgc1c2:i386 1:7.4.2-8.3 1:7.6.4-0.4
 2018-09-15 10:25:39 upgrade libgtksourceview-3.0-common:all 3.24.8-1
 3.24.9-1
 2018-09-15 10:31:45 upgrade libgweather-3-15:i386 3.28.1-1 3.28.2-1
 }}}
 The system was heavily swapping during the upgrade and load was at 8 for
 long periods of time, so maybe I/O timout again.

 Found users who caught the same:
 https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1656065
 https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1766875
 https://forums.linuxmint.com/viewtopic.php?t=266558

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

2018-08-16 Thread 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: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

2018-08-13 Thread 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:
--+---
Changes (by gk):

 * status:  new => needs_information


Comment:

 Tor Browser 8.0a9 ships with OpenSSL 1.0.2o which is used when starting
 Tor Browser regularly via the usual start script (which is for instance
 setting `LD_LIBRARY_PATH` to point to the OpenSSL lib we actually ship).

 Regarding the segfault and I/O errors: What is a vanilla Firefox 60 ESR
 doing in your example scenario? If it behaves the same please file
 upstream bugs (and link to them from this ticket) for Mozilla being at
 least aware of this issue.

--
Ticket URL: 
Tor Bug Tracker & Wiki 
The Tor Project: anonymity online
___
tor-bugs mailing list
tor-bugs@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs

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

2018-08-12 Thread Tor Bug Tracker & Wiki
#27110: TBB segfaults on I/O error and silently fails to restart
--+--
 Reporter:  traumschule   |  Owner:  tbb-team
 Type:  defect| Status:  new
 Priority:  Medium|  Milestone:
Component:  Applications/Tor Browser  |Version:
 Severity:  Normal|   Keywords:
Actual Points:|  Parent ID:
   Points:|   Reviewer:
  Sponsor:|
--+--
 After turning off an external drive, TBB 8.0a9 was started from, it
 segfaults:

 {{{
 Aug 12 13:47:17 x86 kernel: [1971770.627095] EXT4-fs warning (device
 dm-6): dx_probe:745: inode #102236259: lblock 0: comm Cache2 I/O: error -5
 reading directory block
 Aug 12 13:47:17 x86 kernel: [1971770.627185] EXT4-fs warning (device
 dm-6): dx_probe:745: inode #102236259: lblock 0: comm Cache2 I/O: error -5
 reading directory block
 Aug 12 13:47:29 x86 kernel: [1971782.202525] EXT4-fs error (device dm-6):
 ext4_find_entry:1437: inode #102236233: comm DOM Worker: reading directory
 lblock 0
 Aug 12 13:47:29 x86 kernel: [1971782.202548] EXT4-fs (dm-6): previous I/O
 error to superblock detected
 Aug 12 13:47:29 x86 kernel: [1971782.202696] Buffer I/O error on dev dm-6,
 logical block 0, lost sync page write
 Aug 12 13:47:59 x86 kernel: [1971812.552221] EXT4-fs error (device dm-6):
 ext4_find_entry:1437: inode #102236256: comm StreamT~s #1422: reading
 directory lblock 0
 Aug 12 13:47:59 x86 kernel: [1971812.552243] EXT4-fs (dm-6): previous I/O
 error to superblock detected
 Aug 12 13:47:59 x86 kernel: [1971812.552398] Buffer I/O error on dev dm-6,
 logical block 0, lost sync page write
 Aug 12 13:49:11 x86 kernel: [1971884.170995] EXT4-fs error (device dm-6):
 ext4_find_entry:1437: inode #101585396: comm Gecko_IOThread: reading
 directory lblock 0
 Aug 12 13:49:11 x86 kernel: [1971884.171023] EXT4-fs (dm-6): previous I/O
 error to superblock detected
 Aug 12 13:49:11 x86 kernel: [1971884.171266] Buffer I/O error on dev dm-6,
 logical block 0, lost sync page write
 Aug 12 13:50:36 x86 kernel: [1971969.303373] EXT4-fs warning (device
 dm-6): dx_probe:745: inode #102236259: lblock 0: comm Cache2 I/O: error -5
 reading directory block
 Aug 12 13:50:38 x86 kernel: [1971971.122734] Chrome_~dThread[20024]:
 segfault at 0 ip af213ca7 sp ae9c6080 error 6 in
 libxul.so[aed68000+6b9e000]
 Aug 12 13:50:38 x86 kernel: [1971971.123304] Chrome_~dThread[3967]:
 segfault at 0 ip af198ca7 sp ae94b080 error 6 in
 libxul.so[aeced000+6b9e000]
 Aug 12 13:50:38 x86 kernel: [1971971.297396] Chrome_~dThread[6821]:
 segfault at 0 ip af1f6ca7 sp ae9a6080 error 6 in
 libxul.so[aed4b000+6b9e000]
 }}}

 This is not unexpected although it could be handled to inform the user and
 close the virtual fs. The left behind process prevents the OS (debian
 buster) to remount the partition. (tor-browser_en-US and a swap partition
 sit on an external drive that wasn't turned on again before resume from
 suspend)

 /media/user/external/src is linked to /home/user/src

 {{{
 $ lsof|grep Browser
 gvfsd-met  5787user  mem   REG  254,2
 327681729380 /home/user/src/tor/tor-browser_en-US/Browser/.local/share
 /gvfs-metadata/home-2c0742ce.log
 gvfsd-met  5787user  mem   REG  254,6
 32768  102238628 /media/user/external/src/tor/tor-browser_en-
 US/Browser/.local/share/gvfs-metadata/uuid-57c3410d-3392-409c-a36d-
 bff9fd86bdfb-fb3931d1.log
 gvfsd-met  5787user  mem   REG  254,6
 37124  102239578 /media/user/external/src/tor/tor-browser_en-
 US/Browser/.local/share/gvfs-metadata/root
 gvfsd-met  5787user  mem   REG  254,6
 32768  102239579 /media/user/external/src/tor/tor-browser_en-
 US/Browser/.local/share/gvfs-metadata/root-5a546c95.log
 gvfsd-met  5787user  mem   REG  254,6
 2068  102238576 /media/user/external/src/tor/tor-browser_en-
 US/Browser/.local/share/gvfs-metadata/uuid-57c3410d-3392-409c-a36d-
 bff9fd86bdfb
 gvfsd-met  5787user  mem   REG  254,2
 20281729336 /home/user/src/tor/tor-browser_en-US/Browser/.local/share
 /gvfs-metadata/home
 gvfsd-met  5787user   10r  REG  254,6
 37124  102239578 /media/user/external/src/tor/tor-browser_en-
 US/Browser/.local/share/gvfs-metadata/root
 gvfsd-met  5787user   11u  REG  254,6
 32768  102239579 /media/user/external/src/tor/tor-browser_en-
 US/Browser/.local/share/gvfs-metadata/root-5a546c95.log
 gvfsd-met  5787user   15r  REG  254,2
 20281729336 /home/user/src/tor/tor-browser_en-US/Browser/.local/share
 /gvfs-metadata/home
 gvfsd-met  5787user   16u  REG  254,2
 327681729380 /home/user/sr