Bug 615093 - [abrt] crash in firefox-3.6.4-1.fc13: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in firefox-3.6.4-1.fc13: Process /usr/lib64/firefox-3.6/firefox ...
Keywords:
Status: CLOSED DUPLICATE of bug 600796
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e155211fd408f8e3628c40327b7...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-15 22:19 UTC by Greg Martyn
Modified: 2010-11-09 13:48 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 13:48:17 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (64.18 KB, text/plain)
2010-07-15 22:19 UTC, Greg Martyn 		no flags Details
View All

Description Greg Martyn 2010-07-15 22:19:48 UTC 
abrt 1.1.1 detected a crash.

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
global_uuid: e155211fd408f8e3628c40327b70b554ae532b54
kernel: 2.6.33.6-147.fc13.x86_64
package: firefox-3.6.4-1.fc13
rating: 4
reason: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Killed firefox after opening a large xml file. It was using all my cpu + ram.
2. Restart firefox. Abrt notices the crash.
3. Restart firefox again. It works
Comment 1 Greg Martyn 2010-07-15 22:19:50 UTC 
Created attachment 432240 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 13:48:17 UTC 

*** This bug has been marked as a duplicate of bug 600796 ***
Comment 3 Karel Klíč 2010-11-09 13:48:17 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #600796.

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