Fedora Account System
Red Hat Associate
Red Hat Customer
abrt 1.0.6 detected a crash. architecture: i686 Attached file: backtrace cmdline: /usr/lib/firefox-3.5.8/firefox comment: I refreshed a Tumblr page using Disqus comments, when Firefox crashed. component: firefox executable: /usr/lib/firefox-3.5.8/firefox kernel: 2.6.31.12-174.2.19.fc12.i686 package: firefox-3.5.8-1.fc12 rating: 4 reason: Process was terminated by signal 11 (Segmentation fault) release: Fedora release 12 (Constantine)
Created attachment 395382 [details] File: backtrace
#3 <signal handler called> No symbol table info available. #4 FireOrClearDelayedEvents (aDocuments=..., aFireEvents=1) at nsDocument.cpp:7541 i = 0 #5 0x043b97d7 in nsDelayedEventDispatcher::Run (this=0xa96119d0) at nsDocument.cpp:7562 No locals. #6 0x049639fd in nsThread::ProcessNextEvent (this=0xb76f40b0, mayWait=1, result=0xbfdd3ecc) at nsThread.cpp:521 notifyGlobalObserver = 1 obs = {<nsCOMPtr_base> = {mRawPtr = 0xb5c6f1f4}, <No data fields>} event = {<nsCOMPtr_base> = {mRawPtr = 0xa96119d0}, <No data fields>} rv = 0 #7 0x0493250a in NS_ProcessNextEvent_P (thread=<value optimized out>, mayWait=1) at nsThreadUtils.cpp:247 val = 1 #8 0x048ae7e8 in nsBaseAppShell::Run (this=0xb5c6f1f0) at nsBaseAppShell.cpp:170 thread = 0xb76f40b0 #9 0x04764433 in nsAppStartup::Run (this=0xb5ca89a0) at nsAppStartup.cpp:193 rv = <value optimized out> -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Thank you for taking the time to submit this bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue. First of all, could please save the output of the following command into a text file: $ rpm -qa *firefox* *mozilla* *flash* *plugin* Please also install debuginfo for Firefox: $ su -c 'debuginfo-install firefox' Then run Firefox inside the gdb debugger. To do so: $ firefox -g Stuff will appear. Ignore this until you get the gdb command prompt, then do: (gdb) run Now, Firefox should start up. Use it and reproduce the crash. When Firefox crashes, you should be back to the gdb prompt. Now do: (gdb) thread apply all backtrace More screens of stuff will occur. Copy all of this part to your editor of choice, such as gedit, and save it as an uncompressed file and attach it to this bug report. (It will probably be a very large file.) We will review this issue again once you've had a chance to attach this information. Thank you, in advance, for your extra efforts. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Created attachment 395695 [details] The backtrace from gdb produced as instructed I only managed to reproduce the bug once in gdb. This is the result of `thread apply all backtrace`.
Created attachment 395697 [details] The result of `rpm -qa` as instructed
First of all, thank you for your extra efforts. I have been asked to ask you if you have the steps we could use to attempt to reproduce this bug? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I have managed to reproduce the bug by repeatedly reloading the following Tumblr blog with Disqus comments, i.e. pressing Ctrl+R before the previous reload has finished. http://clearsimplewrong.tumblr.com/post/402481875/my-thoughts-about-brian-carpers-rpg-post#disqus_thread The curious thing about Disqus is that the comments are added to the page dynamically. Maybe that has something to do with the crash.
OK, all logs aboard, repro steps given, passing this on. Setting keyword, status and assigning. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Moved upstream as https://bugzilla.mozilla.org/show_bug.cgi?id=551448