Bug 579395

Summary: [abrt] crash in firefox-3.5.9-1.fc12: Process /usr/lib64/firefox-3.5.9/firefox was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Łukasz Łucka <lukaszlucka>
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: 12CC: campbecg, eduar2tole2, gecko-bugs-nobody
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:334d0e796d90ee1477f9109e60d1995cf4eb3a27
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-08 15:18:42 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 Łukasz Łucka 2010-04-04 22:36:39 UTC 
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/firefox-3.5.9/firefox
component: firefox
executable: /usr/lib64/firefox-3.5.9/firefox
kernel: 2.6.32.10-90.fc12.x86_64
package: firefox-3.5.9-1.fc12
rating: 4
reason: Process /usr/lib64/firefox-3.5.9/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
Comment 1 Łukasz Łucka 2010-04-04 22:36:42 UTC 
Created attachment 404428 [details]
File: backtrace
Comment 2 Eduardo Toledo 2010-04-08 19:47:56 UTC 

How to reproduce
-----
1.closed firefox
2.
3.
Comment 3 Eduardo Toledo 2010-04-09 02:50:40 UTC 

How to reproduce
-----
1.close firefox
2.nothing more..
3.
Comment 4 Chris Campbell 2010-05-08 15:18:42 UTC 
Thank you for taking the time to submit this bug report.

This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.



-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

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