Bug 652929 - [abrt] firefox-3.6.12-1.fc14: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
Summary: [abrt] firefox-3.6.12-1.fc14: Process /usr/lib/firefox-3.6/firefox was killed...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 14
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:262b6ee0638757d74b03896b380...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-13 15:24 UTC by meme23
Modified: 2011-12-07 13:03 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-07 13:03:23 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (68.64 KB, text/plain)
2010-11-13 15:24 UTC, meme23
no flags Details

Description meme23 2010-11-13 15:24:54 UTC
abrt version: 1.1.13
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
kernel: 2.6.35.6-48.fc14.i686.PAE
package: firefox-3.6.12-1.fc14
rating: 4
reason: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1289659497
uid: 500

How to reproduce
-----
1. Not sure. I think this happened twice, once late last night where it apparently killed Xorg in the process. 
2. This latest time Firefox hadn't been running but a few minutes. 
3.

Comment 1 meme23 2010-11-13 15:24:58 UTC
Created attachment 460246 [details]
File: backtrace

Comment 2 Martin Stransky 2011-12-07 13:03:23 UTC
We're using mozilla crash reporter now, ABRT is no more used for Firefox/Thunderbird. If you can reliably reproduce the crash (you have a testcase, reproduction steps, etc.) please reopen the bug and attach the reproduction info and assign it directly to me (stransky@redhat.com).

Thanks!


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