Bug 663184

Summary: [abrt] firefox-3.6.13-1.fc13: PR_Abort: Process /usr/lib64/firefox-3.6/firefox was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Calvinhac Bruno <bcalvinhac>
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: dwreski, friedeas, gecko-bugs-nobody, stransky
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:0868426b6b62f002a64e13006bca60f1422ee57d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-17 08:14:23 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 Calvinhac Bruno 2010-12-14 21:52:03 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/firefox-3.6/firefox -UILocale fr
component: firefox
crash_function: PR_Abort
executable: /usr/lib64/firefox-3.6/firefox
kernel: 2.6.34.7-63.fc13.x86_64
package: firefox-3.6.13-1.fc13
rating: 4
reason: Process /usr/lib64/firefox-3.6/firefox was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1292362275
uid: 500

How to reproduce
-----
1.fermeture de firefox ... ?
2.
3.
Comment 1 Calvinhac Bruno 2010-12-14 21:52:06 UTC 
Created attachment 468710 [details]
File: backtrace
Comment 2 Andreas Friedel 2010-12-16 23:31:28 UTC 
Package: firefox-3.6.13-1.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. Closed Firefox
Comment 3 Dave 2010-12-17 04:23:12 UTC 
Package: firefox-3.6.13-1.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. Exiting Firefox
2.
3.
Comment 4 Martin Stransky 2010-12-17 08:14:23 UTC 

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