Bug 646825 - [abrt] firefox-3.6.10-1.fc14: Process /usr/lib/firefox-3.6/firefox was killed by signal 6 (SIGABRT)
Summary: [abrt] firefox-3.6.10-1.fc14: Process /usr/lib/firefox-3.6/firefox was killed...
Keywords:
Status: CLOSED DUPLICATE of bug 611544
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 14
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:15ba9fbccefea5ee4addf412291...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-26 11:54 UTC by cornel panceac
Modified: 2010-11-09 16:12 UTC (History)
1 user (show)

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

Attachments (Terms of Use)
File: backtrace (104.88 KB, text/plain)
2010-10-26 11:54 UTC, cornel panceac 		no flags Details
View All

Description cornel panceac 2010-10-26 11:54:37 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.35.6-43.fc14.i686.PAE
package: firefox-3.6.10-1.fc14
rating: 4
reason: Process /usr/lib/firefox-3.6/firefox was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1288093517
uid: 500

How to reproduce
-----
1.
2.
3.

how did this happen:
open link(s) in new tab(s) , it worked once, twice, etc, then at the last open_tab attempt,  it crashed.
Comment 1 cornel panceac 2010-10-26 11:54:40 UTC 
Created attachment 455744 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 16:12:11 UTC 

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

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