Bug 636191 - [abrt] firefox-3.6.7-1.fc13: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
Summary: [abrt] firefox-3.6.7-1.fc13: Process /usr/lib/firefox-3.6/firefox was killed ...
Keywords:
Status: CLOSED DUPLICATE of bug 625048
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:71f1f6ef4b5f83158664b19d78c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-21 16:03 UTC by Kelly Netterville
Modified: 2010-11-09 15:36 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 15:36:42 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (68.24 KB, text/plain)
2010-09-21 16:03 UTC, Kelly Netterville
no flags Details

Description Kelly Netterville 2010-09-21 16:03:41 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.33.6-147.2.4.fc13.i686
package: firefox-3.6.7-1.fc13
rating: 4
reason: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1285084625
uid: 500

How to reproduce
-----
1. Firefox was open and I was watching an online video (not sure about format - web-based from a php page).
2. I had an earlier java crash (had not rebooted since).

Comment 1 Kelly Netterville 2010-09-21 16:03:43 UTC
Created attachment 448731 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 15:36:42 UTC

*** This bug has been marked as a duplicate of bug 625048 ***

Comment 3 Karel Klíč 2010-11-09 15:36:42 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 #625048.

Sorry for the inconvenience.


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