abrt 1.0.7 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: /usr/lib64/firefox-3.5.8/firefox https://bugzilla.redhat.com/show_bug.cgi?id=568143 comment: I was browsing CNN in Firefox, and it crashed when I clicked a link component: firefox executable: /usr/lib64/firefox-3.5.8/firefox kernel: 2.6.31.12-174.2.22.fc12.x86_64 package: firefox-3.5.8-1.fc12 rating: 4 reason: Process /usr/lib64/firefox-3.5.8/firefox was killed by signal 11 (SIGSEGV) release: Fedora release 12 (Constantine)
Created attachment 396783 [details] File: backtrace
#2 <signal handler called> No symbol table info available. #3 SelectorMatches (data=..., aSelector=0x6e007fdaf1887fb0, aStateMask=0, aAttribute=0x0, aForStyling=1, aDependence=0x0) at nsCSSRuleProcessor.cpp:1214 result = <value optimized out> isNegated = <value optimized out> setNodeFlags = <value optimized out> IDList = <value optimized out> #4 0x00000032102a7fbc in ContentEnumFunc (aRule=0x2e007fdaf18cf0d0, aSelector=0x6e007fdaf1887fb0, aData=0x7fffadfa0080) at nsCSSRuleProcessor.cpp:1888 data = 0x7fffadfa0080 #5 0x00000032102a8304 in RuleHash::EnumerateAllRules (this=0x7fdaf1898480, aNameSpace=<value optimized out>, aTag=<value optimized out>, aID=<value optimized out>, aClassList=0x7fdaefaed890, aFunc=<value optimized out>, aData=0x7fffadfa0080) at nsCSSRuleProcessor.cpp:630 valueIndex = <value optimized out> highestRuleIndex = <value optimized out> cur = 0x7fdaf28a8b70 next = <value optimized out> value = <value optimized out> classCount = 2 testCount = <value optimized out> valueCount = 3 #6 0x00000032102a8e9b in nsCSSRuleProcessor::RulesMatching ( this=<value optimized out>, aData=0x7fffadfa0080) at nsCSSRuleProcessor.cpp:1919 cascade = <value optimized out> #7 0x00000032102d3839 in EnumRulesMatching ( aProcessor=<value optimized out>, aData=<value optimized out>) at nsStyleSet.cpp:409 data = <value optimized out> -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
If this is a reproducible crash, could we get you to please: 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 we get output of the command, saved in a text file and attached to this bug: $ rpm -qa *xulrun* *firefox* *mozilla* *flash* *plugin* Please also install firefox-debuginfo. # debuginfo-install firefox Then run firefox inside the gdb debugger. Please do the following: $ 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 back-trace 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. We will review this issue again once you've had a chance to attach this information. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I apologize for the wait, but I hope to get the above steps executed this evening.
I should note that I've not seen this crash in the last two days, but I haven't been paying attention to what updates yum is tossing my way. I'll check on that as well.
Reporter, no worries. Let us know when you can. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
I've been hit by the rash of NetworkManager related issues lately and I've been unable to connect to the net to attempt recreating this issue.
Huzzah! I received a similar crash yesterday and I think I've made a correlation. I had just updated via YUM which included the new version of FireFox. I already had FireFox open as this was updating, and once I began typing in the Google search toolbar the crash occurred. I shut down FireFox, waited for the YUM update to complete, opened FireFox again and haven't been able to reproduce the crash.
Passing this on to Martin. Reproduction steps are listed, such as they are. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
*** This bug has been marked as a duplicate of bug 489306 ***