Summary: | www/tor-browser 12.0.6_1 Segfault after a few seconds of launch the port | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Ports & Packages | Reporter: | Bob Slacker <bobslacker> | ||||||||||
Component: | Individual Port(s) | Assignee: | freebsd-ports-bugs (Nobody) <ports-bugs> | ||||||||||
Status: | Closed Overcome By Events | ||||||||||||
Severity: | Affects Some People | CC: | arrowd, bgroper, bobslacker, dan.kotowski, desktop, fernape, freebsd, markusalbertgraf | ||||||||||
Priority: | --- | Keywords: | crash, needs-qa | ||||||||||
Version: | Latest | Flags: | fernape:
maintainer-feedback?
(freebsd) |
||||||||||
Hardware: | amd64 | ||||||||||||
OS: | Any | ||||||||||||
URL: | https://forums.freebsd.org/threads/tor-browser-segfault-after-upgrading-to-2023q3.89615/ | ||||||||||||
See Also: | https://bugzilla.mozilla.org/show_bug.cgi?id=1731142 | ||||||||||||
Attachments: |
|
Description
Bob Slacker
2023-07-10 13:19:26 UTC
Created attachment 243364 [details]
backtrace
Backtrace from .core file on 14.0-CURRENT
Created attachment 243365 [details] the backtrace, in colour (In reply to Graham Perrin from comment #1) I encountered the crash with a first run of this version, maybe after clicking away (or Alt-Tab away) from a pop-up near top right. So far, no crash with subsequent runs. (In reply to Graham Perrin from comment #3) Same happens to me, if I change my workspace or change the focused app, tor-browser crashes almost immediately. It's also crashes when I try to load any onion site. tor-browser frequently crashing here too. The recent upgrade included some unintended new features. This issue it is present in the version www/tor-browser-12.0.6_3 present in the latest repository as well. Same here on FreeBSD 13.2. tor-browser-12.0.6 used core dump on first opening a page, after upgrade to tor-browser-12.0.6_4 will open the first page but still dumps sporadically. Really strange, I can't see these crashes on 13.2-RELEASE and tor-browser 12.0.6_4. I just installed the browser, started the tor service and it seems I can access different .onion sites without problem. Created attachment 245009 [details] (gdb) bt (In reply to Graham Perrin from comment #1) > Backtrace from .core file on 14.0-CURRENT Without attempting to compare the two: here's a gdb view of a backtrace from a crash of tor-browser-12.0.6_4 on FreeBSD 15.0-CURRENT 1500000. gdb /usr/local/bin/tor-browser -- ~/tor-browser.core Created attachment 245010 [details] (lldb) bt, bt all (In reply to Graham Perrin from comment #9) > … here's a gdb view of a backtrace from a crash … This lldb view seems less useful than the gdb view. lldb -c ~/tor-browser.core (In reply to Bob Slacker from comment #0) If you refrain from resizing any browser window, then is the crash reproducible? jbeich@ you have a good nose for things such as this. For me at the moment, crashes are consistently reproducible in multiple ways. One set of steps: 1. maximise the browser window 2. use the File menu, or tab bar, to open a new tab – a crash before the tab appears. Given (1) above and (a) below, what's the aroma? ---- (In reply to Fernando Apesteguía from comment #8) Try these two steps: a) Control-B (to open the sidebar) b) use the sidebar to open any bookmark. (In reply to Graham Perrin from comment #11) Yes, the crash is reproducible without resizing the window. Often the right click at a link (ie open in new tab) will cause a crash. (In reply to Graham Perrin from comment #12) That triggers the crash in my case. Having a look at the backtrace, it seems similar to this Firefox report: https://bugzilla.mozilla.org/show_bug.cgi?id=1731142 which is still open. I obtain a very similar backtrace: #0 0x00001592741f3c5a in thr_kill () at /lib/libc.so.7 #1 0x000015927416c6d4 in raise () at /lib/libc.so.7 #2 0x00001592a3341a02 in nsProfileLock::FatalSignalHandler(int, __siginfo*, void*) () at /usr/local/lib/tor-browser/libxul.so #3 0x00001592a3cd4997 in WasmTrapHandler(int, __siginfo*, void*) () at /usr/local/lib/tor-browser/libxul.so #4 0x0000159272915b6e in () at /lib/libthr.so.3 #5 0x000015927291511f in () at /lib/libthr.so.3 #6 0x00007fffffffe8a3 in <signal handler called> () #7 0x00001592e75542e0 in () #8 0x00001592a4beadba in style::properties::cascade::Cascade::apply_properties::h62ca68d5fcc77c39 () at /usr/local/lib/tor-browser/libxul.so #9 0x00001592a4bea5f7 in style::properties::cascade::cascade_rules::h14b1cfa99da11f4b () at /usr/local/lib/tor-browser/libxul.so #10 0x00001592a4c017f6 in style::stylist::Stylist::cascade_style_and_visited::h519b00bebdda9c12 () at /usr/local/lib/tor-browser/libxul.so #11 0x00001592a4bf382d in style::style_resolver::StyleResolverForElement<E>::cascade_style_and_visited::had2d5ef70f7a19da () at /usr/local/lib/tor-browser/libxul.so #12 0x00001592a4bf34d8 in style::style_resolver::StyleResolverForElement<E>::cascade_primary_style::hc5db7f434411e767 () at /usr/local/lib/tor-browser/libxul.so (In reply to Graham Perrin from comment #12) Bug 273999 comment 4 noted and understood; feedback request cancelled. (In reply to Fernando Apesteguía from comment #14) Thanks, I'll raise this in <https://matrix.to/#/#developers:mozilla.org> <https://matrix.to/#/!lrZtdjyLpBmoKbMdyx:mozilla.org/$IyCTCLC6bkOjLCrIkuJvCUF3Vvk1wC83sX7PbfTrXFE?via=mozilla.org&via=matrix.org&via=igalia.com> led to <https://bugzilla.mozilla.org/show_bug.cgi?id=1731142#c13> comments 13, 14, 15 … <https://github.com/freebsd/poudriere/discussions/1077> > www/tor-browser DEBUG off after building with DEBUG=on · freebsd/poudriere · > Discussion #1077 (In reply to Bob Slacker from comment #0) You try to update to 13.0.1 (In reply to Martin Filla from comment #18) Yes, now on FBSD 13.3 and tor-browser 13.0.1 the crash went way. I still have some issues accessing some onions (dread for ex.) but this is probably not related with this old bug. |