abrt 1.1.1 detected a crash. architecture: i686 Attached file: backtrace cmdline: /usr/lib/firefox-3.6/firefox component: firefox crash_function: nsProfileLock::FatalSignalHandler executable: /usr/lib/firefox-3.6/firefox global_uuid: 28af114c40b95cb06b562786ca28458424e9a9ed kernel: 2.6.33.5-112.fc13.i686 package: firefox-3.6.3-4.fc13 rating: 4 reason: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard) How to reproduce ----- 1.Launch Firefox, program segfaults before GUI is displayed. 2. 3.
Created attachment 422404 [details] File: backtrace
Thank you for taking the time to report this bug. Updates to this package have been released since it was first reported. If you have time to update the package and re-test, please do so and report the results here. You can obtain the updated package by typing 'yum update <package>' or using the graphical updater, Software Update. Disable extensions, plugins and non-default themes. Clear cookies and cache. Exit the browser completely. Then restart the browser and attempt to replicate the crash. #3 <signal handler called> No symbol table info available. #4 0x026a87cb in nsHtml5ElementName () at nsHtml5ElementName.cpp:96 No locals. #5 nsHtml5ElementName::initializeStatics () at nsHtml5ElementName.cpp:157 No locals. #6 0x026dac82 in nsHtml5Module::InitializeStatics () at nsHtml5Module.cpp:60 No locals. #7 0x02337e41 in nsLayoutStatics::Initialize () at nsLayoutStatics.cpp:274 rv = <value optimized out> #8 0x02336314 in Initialize (aSelf=0xb38b7c70) at nsLayoutModule.cpp:351 rv = <value optimized out> observerService = warning: can't find linker symbol for virtual table for `nsCOMPtr<nsIObserverService>' value {<nsCOMPtr_base> = {mRawPtr = 0x23362ee}, <No data fields>} -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Reporter, after disabling all plug-ins is this crash still an issue for you? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as INSUFFICIENT_DATA. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers