Bug 623455 - [abrt] firefox-3.6.4-2.fc14: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
Summary: [abrt] firefox-3.6.4-2.fc14: Process /usr/lib64/firefox-3.6/firefox was kille...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: rawhide
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:8ba4d7e894083208f11f49f99cd...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-11 20:06 UTC by Matt Hooper
Modified: 2011-12-07 13:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-07 13:09:56 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (107.89 KB, text/plain)
2010-08-11 20:06 UTC, Matt Hooper 		no flags Details
View All

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!
Note You need to log in before you can comment on or make changes to this bug.