Bug 684228 - [abrt] firefox-3.6.10-1.fc14: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
Summary: [abrt] firefox-3.6.10-1.fc14: Process /usr/lib/firefox-3.6/firefox was killed...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:bf10e1f0b8e2274d2d630cf595d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-11 14:32 UTC by Andy Simpson
Modified: 2011-12-07 13:06 UTC (History)
1 user (show)

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

Attachments (Terms of Use)
File: backtrace (31.86 KB, text/plain)
2011-03-11 14:32 UTC, Andy Simpson 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Andy Simpson 2011-03-11 14:32:36 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: /usr/lib/firefox-3.6/firefox
component: firefox
executable: /usr/lib/firefox-3.6/firefox
kernel: 2.6.33.3-85.fc13.i686.PAE
package: firefox-3.6.10-1.fc14
rating: 4
reason: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1299823872
uid: 500

How to reproduce
-----
1.
2.
3.
During yum update in background (900 plus MB's worth of updates) immediately after upgrading from Fedora 13 to 14  Firefox was running during the update process
Comment 1 Andy Simpson 2011-03-11 14:32:38 UTC 
Created attachment 483738 [details]
File: backtrace
Comment 2 Martin Stransky 2011-12-07 13:06:22 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.