Opened 6 months ago

Last modified 6 months ago

#27940 needs_information defect

8.0.2 crashed closing a busy tab

Reported by: traumschule Owned by: tbb-team
Priority: High Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: tbb-crash, tbb-8.0-issues
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

(debian buster 32-bit)

Thanks for this new version!
The update went fine (although i had to manually trigger it and the automatic updater found none, the log shows no time though).

What happened:

  • clicked on the X of a tab which was busy
  • TB disappeared

The js error is probably unrelated since the log is full of it:

JavaScript error: chrome://global/content/browser-child.js, line 359: NS_ERROR_NOT_AVAILABLE: Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIWebNavigation.loadURIWithOptions]
JavaScript error: chrome://global/content/browser-child.js, line 359: NS_ERROR_NOT_AVAILABLE: Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIWebNavigation.loadURIWithOptions]
JavaScript error: chrome://global/content/browser-child.js, line 359: NS_ERROR_NOT_AVAILABLE: Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIWebNavigation.loadURIWithOptions]
./start-tor-browser: line 373: 25000 Segmentation fault      TOR_CONTROL_PASSWD=${TOR_CONTROL_PASSWD} ./firefox --class "Tor Browser" -profile TorBrowser/Data/Browser/profile.default "${@}" < /dev/null

Would love to give you a trace but #26323 (#26462)

Child Tickets

Attachments (1)

tb8.0.2-crash.log (21.8 KB) - added by traumschule 6 months ago.

Download all attachments as: .zip

Change History (3)

Changed 6 months ago by traumschule

Attachment: tb8.0.2-crash.log added

comment:1 Changed 6 months ago by gk

Keywords: tbb-8.0-issues added
Priority: MediumHigh
Status: newneeds_information

Can you reproduce that? If so, can you reproduce that with older Tor Browser 8 versions? (see: https://archive.torproject.org/tor-package-archive/torbrowser/) I wonder whether you are "just" hitting 32bit limitations here.

comment:2 in reply to:  1 Changed 6 months ago by traumschule

Replying to gk:

Can you reproduce that?

Not yet, but i found this in syslog which relates it to #27110 (at least the error 6, the symbols are different but this doesn't necessarily mean anything because it was a different version):

Oct  3 12:50:57 host kernel: [178581.786424] Chrome_~dThread[5296]: segfault at 0 ip af0fa117 sp ad82c080 error 6 in libxul.so[aec4e000+6bb2000]
Oct  3 12:50:57 host kernel: [178581.786438] Code: 00 00 00 0f 0b 8d b6 00 00 00 00 8b 46 1c 85 c0 74 95 5b 89 f0 5e 5f e9 87 bf ff ff 8b 83 b0 fb ff ff 8d 93 e8 cc 96 fc 89 10 <c7> 05 00 00 00 00 00 00 00 00 0f 0b 8d b6 00 00 00 00 8d bc 27 00 
Oct  3 12:50:57 host kernel: [178581.786739] Chrome_~dThread[5266]: segfault at 0 ip af169117 sp ad89b080 error 6 in libxul.so[aecbd000+6bb2000]
Oct  3 12:50:57 host kernel: [178581.786745] Code: 00 00 00 0f 0b 8d b6 00 00 00 00 8b 46 1c 85 c0 74 95 5b 89 f0 5e 5f e9 87 bf ff ff 8b 83 b0 fb ff ff 8d 93 e8 cc 96 fc 89 10 <c7> 05 00 00 00 00 00 00 00 00 0f 0b 8d b6 00 00 00 00 8d bc 27 00 
Oct  3 12:50:57 host kernel: [178581.787042] Chrome_~dThread[5221]: segfault at 0 ip af182117 sp ad8b4080 error 6 in libxul.so[aecd6000+6bb2000]
Oct  3 12:50:57 host kernel: [178581.787048] Code: 00 00 00 0f 0b 8d b6 00 00 00 00 8b 46 1c 85 c0 74 95 5b 89 f0 5e 5f e9 87 bf ff ff 8b 83 b0 fb ff ff 8d 93 e8 cc 96 fc 89 10 <c7> 05 00 00 00 00 00 00 00 00 0f 0b 8d b6 00 00 00 00 8d bc 27 00
Oct  3 12:50:57 host kernel: [178581.809550] Chrome_~dThread[5154]: segfault at 0 ip af193117 sp ad8c5080 error 6 in libxul.so[aece7000+6bb2000]
Oct  3 12:50:57 host kernel: [178581.809563] Code: 00 00 00 0f 0b 8d b6 00 00 00 00 8b 46 1c 85 c0 74 95 5b 89 f0 5e 5f e9 87 bf ff ff 8b 83 b0 fb ff ff 8d 93 e8 cc 96 fc 89 10 <c7> 05 00 00 00 00 00 00 00 00 0f 0b 8d b6 00 00 00 00 8d bc 27 00
Note: See TracTickets for help on using tickets.