Bug 75045
| Summary: | www/firefox still crashing upon print | ||
|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Frank Altpeter <frank.altpeter> |
| Component: | Individual Port(s) | Assignee: | freebsd-gnome (Nobody) <gnome> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | Latest | ||
| Hardware: | Any | ||
| OS: | Any | ||
Responsible Changed From-To: freebsd-ports-bugs->gnome Over to GNOME-team State Changed From-To: open->closed This should be fixed in Firefox 1.0_5,1. |
Although this bug should be gone since 1.0_3, it still happens with the current 1.0_4,1 port version. But not allways, though. I wasn't yet able to find out, on which constellation firefox does crash when trying to print something, but mostly it does work again for some time after restart. I thought it would have to do with extensions but even with a clean fresh $HOME/.mozilla it still does crash sporadically. Since strace and truss are not very suitable here, i'm willing to test further when someone can tell me how to gather more information on that topic. The first 10 lines of gdb backtrace on the core tells: #0 0x2899af17 in pthread_testcancel () from /usr/lib/libpthread.so.1 #1 0x2898c0b5 in sigaction () from /usr/lib/libpthread.so.1 #2 0x289861e1 in pthread_kill () from /usr/lib/libpthread.so.1 #3 0x28985bb0 in raise () from /usr/lib/libpthread.so.1 #4 0x080554a3 in nsProfileLock::FatalSignalHandler () #5 0x2898ac16 in sigaction () from /usr/lib/libpthread.so.1 #6 0x2898aa97 in sigaction () from /usr/lib/libpthread.so.1 #7 0x2898b619 in sigaction () from /usr/lib/libpthread.so.1 #8 0x28993b3f in pthread_mutexattr_init () from /usr/lib/libpthread.so.1 #9 0x28993a2e in pthread_mutexattr_init () from /usr/lib/libpthread.so.1 #10 0x28a41c5f in _ctx_start () from /lib/libc.so.5 If of interest, my system is an intel centrino notebook (ibm thinkpad t40) and my print suite is CUPS-1.1.22 (all ports up-to-date) I considered this a critical bug, since you can run in great problems for example if you try to print out a train ticket online (or any other important only-once-generated dta) and your browser does crash, and your ticket is lost. How-To-Repeat: Don't know, just surf around a bit and then try to print something - sometimes it happens, sometimes not.