abrt 1.1.1 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: /usr/lib64/firefox-3.6/firefox comment: I reloaded a web page. component: firefox crash_function: nsProfileLock::FatalSignalHandler executable: /usr/lib64/firefox-3.6/firefox global_uuid: 4ca65d4243ab60d0091d1fdc67bfca8e85bb36c6 kernel: 2.6.33.5-112.fc13.x86_64 package: firefox-3.6.3-4.fc13 rating: 4 reason: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard)
Created attachment 421436 [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. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
(In reply to comment #2) > 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. > > > > > -- > Fedora Bugzappers volunteer triage team > https://fedoraproject.org/wiki/BugZappers I've updated and so far so good. No crashes, but the problem was intermittent to begin with.
Is it OK to close this bug report with CURRENTRELEASE ?
Yes, I think so.