Bug 689355 - [abrt] firefox-3.6.15-1.fc14: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
Summary: [abrt] firefox-3.6.15-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
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:49d3ad12a65f3875325f6508062...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-21 07:27 UTC by Bruce Barbour
Modified: 2011-12-07 13:19 UTC (History)
1 user (show)

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


Attachments (Terms of Use)
File: backtrace (60.56 KB, text/plain)
2011-03-21 07:27 UTC, Bruce Barbour
no flags Details

Description Bruce Barbour 2011-03-21 07:27:37 UTC
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 62018 bytes
cmdline: /usr/lib/firefox-3.6/firefox
comment: Cannot recall particular action, noticed red alarm icon but just deleted it as unimportant.
component: firefox
Attached file: coredump, 286339072 bytes
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib/firefox-3.6/firefox
kernel: 2.6.35.11-83.fc14.i686.PAE
package: firefox-3.6.15-1.fc14
rating: 4
reason: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1300677982
uid: 500

How to reproduce
-----
1.Unknown
2.
3.

Comment 1 Bruce Barbour 2011-03-21 07:27:39 UTC
Created attachment 486555 [details]
File: backtrace

Comment 2 Martin Stransky 2011-12-07 13:19:35 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).

Thanks!


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