Bug 653147 - [abrt] firefox-3.6.12-1.fc14: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
Summary: [abrt] firefox-3.6.12-1.fc14: Process /usr/lib64/firefox-3.6/firefox was kill...
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 14
Hardware: x86_64
OS: Unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:d55f6ebf0d612359ab116d898e6...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-11-14 17:28 UTC by Georg Wittig
Modified: 2010-12-17 19:08 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-12-17 19:08:41 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (97.90 KB, text/plain)
2010-11-14 17:28 UTC, Georg Wittig
no flags Details

Description Georg Wittig 2010-11-14 17:28:38 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/firefox-3.6/firefox
component: firefox
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/firefox-3.6/firefox
package: firefox-3.6.12-1.fc14
rating: 4
reason: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1289752729
uid: 2830

How to reproduce
Don't know how to reproduce.
Firefox was running a couple of hours. I didn't use it for half an hour or so.
Then I noticed firefox had crashed for some reason.

Comment 1 Georg Wittig 2010-11-14 17:28:42 UTC
Created attachment 460387 [details]
File: backtrace

Comment 2 Chris Campbell 2010-12-17 19:08:41 UTC
Reporter, there is nothing glaringly obvious in the included back-trace. Without being able to reproduce the crash, there is no way we can begin to pin-point the root cause. I am therefore setting this report to closed as INSUFFICIENT_DATA. If you or anyone else has the exact same crash, ABRT will flag it as a duplicate.

If you disagree with this determination, please feel free to re-open this report at any time.

Fedora Bugzappers volunteer triage team

Note You need to log in before you can comment on or make changes to this bug.