abrt 1.0.8 detected a crash. architecture: i686 Attached file: backtrace cmdline: /usr/lib/firefox-3.5.8/firefox component: firefox executable: /usr/lib/firefox-3.5.8/firefox kernel: 2.6.32.9-70.fc12.i686.PAE package: firefox-3.5.8-1.fc12 rating: 3 reason: Process /usr/lib/firefox-3.5.8/firefox was killed by signal 11 (SIGSEGV) release: Fedora release 12 (Constantine) How to reproduce ----- 1. Firefox crashed while I was not using it actively (91 open tabs). 2. 3.
Created attachment 404308 [details] File: backtrace
#3 <signal handler called> No symbol table info available. #4 0x0146c866 in RenderInstaller::requestConfiguration(std::basic_string<char, std::char_traits<char>, std::allocator<char> > const&) () from /usr/lib/mozilla/plugins/libnpmyvrlx.so No symbol table info available. #5 0x0146cd3b in RenderInstaller::requestConfigFile() () from /usr/lib/mozilla/plugins/libnpmyvrlx.so No symbol table info available. #6 0x0146f928 in RenderInstaller::run() () from /usr/lib/mozilla/plugins/libnpmyvrlx.so No symbol table info available. #7 0x01476005 in MThread::threadEntry(void*) () from /usr/lib/mozilla/plugins/libnpmyvrlx.so No symbol table info available. #8 0x00aa4ab5 in start_thread (arg=<value optimized out>) at pthread_create.c:297 __res = <value optimized out> __ignore1 = 3 __ignore2 = -1471262080 now = <value optimized out> unwind_buf = {cancel_jmp_buf = {{jmp_buf = {11231220, 0, 4001536, -1717570440, -45743362, -1774966324}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, canceltype = 0}}} not_first_call = <value optimized out> pagesize_m1 = <value optimized out> freesize = <value optimized out> #9 0x009cfdce in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 No locals. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Thank you for taking the time to report this crash. Unfortunately, the stack trace is not very useful in determining the cause of the crash, because it lacks debugging symbols. This is likely due to a bug in ABRT, which should have captured this information automatically. I am reassigning this bug to ABRT for diagnosis; if it can be fixed, you should be able to automatically generate a useful report for this crash in the future. In the meantime, if you are interested in attempting to diagnose the crash itself, you can try installing debuginfo packages manually, which will hopefully provide debugging symbols in the next stack trace. You can run the command: debuginfo-install PROGRAMNAMEHERE Please see http://fedoraproject.org/wiki/StackTraces for more information about obtaining stack traces manually. If you successfully obtain a better stack trace, please report it under a separate bug and add a comment to this bug with the new bug number (since this bug will track the ABRT fix, not the crash fix). -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '12'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Ok to close, I have not experienced this problem either since then and at least not for a long time.
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.