Bug 682630 - [abrt] firefox-3.6.14-1.fc14: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
Summary: [abrt] firefox-3.6.14-1.fc14: Process /usr/lib64/firefox-3.6/firefox was kill...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:2d0da036d6d3eb3fab790114a57...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-07 05:04 UTC by Paul Thomas
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:12 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (65.73 KB, text/plain)
2011-03-07 05:04 UTC, Paul Thomas 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Paul Thomas 2011-03-07 05:04:01 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 67310 bytes
cmdline: /usr/lib64/firefox-3.6/firefox
component: firefox
Attached file: coredump, 245813248 bytes
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/firefox-3.6/firefox
kernel: 2.6.35.11-83.fc14.x86_64
package: firefox-3.6.14-1.fc14
rating: 4
reason: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1299472712
uid: 500

How to reproduce
-----
1. closed firefox after graphics got scrambled
Comment 1 Paul Thomas 2011-03-07 05:04:04 UTC 
Created attachment 482598 [details]
File: backtrace
Comment 2 Martin Stransky 2011-12-07 13:03:12 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.