User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:188.8.131.52) Gecko/2009060310 Ubuntu/8.10 (intrepid) Firefox/3.0.11 GTB5 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:184.108.40.206) Gecko/2009060310 Ubuntu/8.10 (intrepid) Firefox/3.0.11 GTB5 I ran Firefox from shell and when it crashed I received the following error in the command line: + Segmentation fault firefox -P "Temp" -no-remote After I get the above error, I cannot execute the command anymore and received another error: /usr/lib/firefox-3.0.11/firefox: symbol lookup error: /usr/lib/libgtk-x11-2.0.so.0: undefined symbol: g_signal_handlers_disconnect_matched I'd be glad to give more details. Please ask... Reproducible: Always Steps to Reproduce: 1.Go to jogli.com 2.listen to music for about 2 hours 3.Firefox crashes I have the following plugins installed: - delicious bookmars - flashblock - google gears - google toolbar - ubuntu firefox modifications
Summary: Firefox crashes after about 2 hours music listening → Firefox crashes after about 2 hours music listening in jogli.com
I have a lot of sites open: - google.com - morfix.co.il - different sites 4 windows ~4 tabs each window Firefox stays up and running for days. When I listen to music in jogli.com - it crashes.
Could you provide the crash report ID from about:crashes?
He is using a Ubuntu Version of Firefox and only original Mozilla.org builds come with our crashreporter. Please read https://developer.mozilla.org/en/How_to_get_a_stacktrace_for_a_bug_report , there should be a link to the Ubunto instructions at the end or you are trying to use an original Mozilla.org build.
I'm reading on how to get the stack trace... Also, i'm positive that it was not one of the plugins I mentioned above. I got the same problem with a clean profile - just the "ubuntu firefox modifications" plugin
I couldn't install the debug thingy. Sorry. I followed ubuntu's instructions and didn't work. At home, on ubuntu 9.04 32bit, i couldn't reproduce during the weekend. It did crashed a week ago on my home computer - perhaps some updated was pushed a few days ago. Anyway, i'll try reproducing it on my work computer ubuntu 32b 8.10 again. If I succeed, perhaps someone can do this as well...
Severity: normal → critical
Crashes after about an hour listening to "The Prodigy" - on ubuntu 8.10 32b.
Alik, any luck of reproducing it on another computer?
It did crash on another 32b - same ubuntu version, but lately it haven't crashed. I upgraded to 9.04 a few days ago and haven't happened since. I'll try it again and tell you the results.
It crashed with the same scenario (Playing The prodigy hits) on ubuntu 9.04 32b. I timed it: $ time firefox Segmentation fault real 8m52.662s user 2m20.009s sys 0m17.213s $
Alik, did you ever try what was suggested in comment #3? That would help out tremendously!
Yep. Tried it and didn't work - as I wrote in comment #5. Am I the only one having this problem? The scenario is very short though takes time to crash (not human hours - machine's). Everyone can do it by creating a new profile, which is what I did, in order not to crash the whole working environment (all open tabs and windows). The link to what I was listening (that crashed) is: http://jogli.com/#item/artist?artist=Prodigy+&auto_redirect=true So, if anyone has the debug thingy installed - he can probably reproduce it and see the full crash report. No one commented that it is not reproducible...
Reporter, please retest with Firefox 3.6.12 or later in a fresh profile (http://support.mozilla.com/kb/Managing+profiles). Also update your plugins (flash, adobe reader, java, quicktime, silverlight, etc/) Go to the developer's website and download the latest version from there.
Whiteboard: [CLOSEME 2010-12-01]
No reply, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.