Bug 692798 - [abrt] firefox-3.6.16-1.fc14: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
Summary: [abrt] firefox-3.6.16-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:f4076b6817f8be6f7de3b91c367...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-01 08:20 UTC by LR
Modified: 2011-12-07 13:10 UTC (History)
1 user (show)

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

Attachments (Terms of Use)
File: backtrace (53.96 KB, text/plain)
2011-04-01 08:20 UTC, LR 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description LR 2011-04-01 08:20:38 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 55257 bytes
cmdline: /usr/lib/firefox-3.6/firefox http://ui.skype.com/ui/2/2.1.0.81/en/go/privacy
component: firefox
Attached file: coredump, 244228096 bytes
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib/firefox-3.6/firefox
kernel: 2.6.35.11-83.fc14.i686
package: firefox-3.6.16-1.fc14
rating: 4
reason: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1301573408
uid: 500

How to reproduce
-----
1.Booting & this happened. Have no other information
2.
3.
Comment 1 LR 2011-04-01 08:20:42 UTC 
Created attachment 489318 [details]
File: backtrace
Comment 2 Martin Stransky 2011-12-07 13:10:50 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.