Bug 651075 - [abrt] firefox-3.6.12-1.fc14: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
Summary: [abrt] firefox-3.6.12-1.fc14: Process /usr/lib64/firefox-3.6/firefox was kill...
Keywords:
Status: CLOSED DUPLICATE of bug 639326
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:0c14628fbf2976ba7881e774803...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-08 19:10 UTC by Gideon Mayhak
Modified: 2010-11-09 12:49 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 12:49:20 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (95.30 KB, text/plain)
2010-11-08 19:10 UTC, Gideon Mayhak 		no flags Details
View All

Description Gideon Mayhak 2010-11-08 19:10:34 UTC 
abrt version: 1.1.13
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
kernel: 2.6.35.6-48.fc14.x86_64
package: firefox-3.6.12-1.fc14
rating: 4
reason: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1289242589
uid: 500

How to reproduce
-----
1. A video was finishing on Hulu in one tab
2. I opened several Phoronix articles in new tabs
3. The browser closed suddenly and ABRT came up
Comment 1 Gideon Mayhak 2010-11-08 19:10:36 UTC 
Created attachment 458853 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 12:49:20 UTC 

*** This bug has been marked as a duplicate of bug 639326 ***
Comment 3 Karel Klíč 2010-11-09 12:49:20 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 #639326.

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