Bug 731659 - [abrt] firefox-3.6.18-1.fc14: skip_variable: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
Summary: [abrt] firefox-3.6.18-1.fc14: skip_variable: Process /usr/lib/firefox-3.6/fir...
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:d5db2b8882fa2be26ab6c21cb5b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-18 09:10 UTC by bumbi_abel@hotmail.com
Modified: 2011-12-07 13:34 UTC (History)
1 user (show)

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


Attachments (Terms of Use)
File: backtrace (77.65 KB, text/plain)
2011-08-18 09:10 UTC, bumbi_abel@hotmail.com
no flags Details

Description bumbi_abel@hotmail.com 2011-08-18 09:10:30 UTC
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 79515 bytes
cmdline: /usr/lib/firefox-3.6/firefox -UILocale sv-SE
component: firefox
Attached file: coredump, 229601280 bytes
crash_function: skip_variable
executable: /usr/lib/firefox-3.6/firefox
kernel: 2.6.35.13-92.fc14.i686
package: firefox-3.6.18-1.fc14
rating: 4
reason: Process /usr/lib/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1313658248
uid: 500

How to reproduce
-----
1.I was looking on Facebook when it crashed
2.
3.

Comment 1 bumbi_abel@hotmail.com 2011-08-18 09:10:33 UTC
Created attachment 518823 [details]
File: backtrace

Comment 2 Martin Stransky 2011-12-07 13:34:03 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.