Bug 623455

Summary: [abrt] firefox-3.6.4-2.fc14: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Matt Hooper <matthew.hooper>
Component: firefoxAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: rawhideCC: gecko-bugs-nobody
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:8ba4d7e894083208f11f49f99cd9e296158ae664
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-07 13:09:56 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 Matt Hooper 2010-08-11 20:06:27 UTC 
abrt version: 1.1.5
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/firefox-3.6/firefox -UILocale en-GB https://bugzilla.redhat.com/show_bug.cgi?id=623442
comment: Was attempting to attach a corrupt JPEG to another bug (#622982, contrary to command details in this bug)  to help in re-producing the issue. I was browsing the folder with the image in at the time of the crash about to select it.
component: firefox
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/firefox-3.6/firefox
global_uuid: 8ba4d7e894083208f11f49f99cd9e296158ae664
kernel: 2.6.35-0.55.rc6.git0.fc14.x86_64
package: firefox-3.6.4-2.fc14
rating: 4
reason: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Rawhide)
time: 1281556588
uid: 500
Comment 1 Matt Hooper 2010-08-11 20:06:35 UTC 
Created attachment 438284 [details]
File: backtrace
Comment 2 Martin Stransky 2011-12-07 13:09:56 UTC 
We're using mozilla crash reporter now, ABRT is no more used for Firefox/Thunderbird. If you can reliably reproduce the crash (you have a testcase, reproduction steps, etc.) please reopen the bug and attach the reproduction info and assign it directly to me (stransky).

Thanks!