Bug 618787

Summary: [abrt] crash in firefox-3.6.7-1.fc13: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Basil Mohamed Gohar <me>
Component: firefoxAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: francis, gecko-bugs-nobody
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:fa3f4dba3eb110223a4f7b57d4e8fe1c615e8aad
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-08 19:14:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Basil Mohamed Gohar 2010-07-27 18:02:05 UTC 
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/firefox-3.6/firefox http://eschool.campfirenow.com/room/171276 http://mail.eschoolconsultants.com
comment: I was switching back-and-forth between Firefox & Aptana (Eclipse) to paste some content, and Firefox suddenly hung and then crashed.
component: firefox
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/firefox-3.6/firefox
global_uuid: fa3f4dba3eb110223a4f7b57d4e8fe1c615e8aad
kernel: 2.6.33.6-147.fc13.x86_64
package: firefox-3.6.7-1.fc13
rating: 4
reason: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Comment 1 Basil Mohamed Gohar 2010-07-27 18:02:10 UTC 
Created attachment 434793 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-08 19:14:26 UTC 

*** This bug has been marked as a duplicate of bug 612293 ***
Comment 3 Karel Klíč 2010-11-08 19:14:26 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 #612293.

Sorry for the inconvenience.