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

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


Attachments (Terms of Use)
File: backtrace (97.23 KB, text/plain)
2011-03-16 06:32 UTC, kovaju
no flags Details

Description kovaju 2011-03-16 06:32:13 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 99563 bytes
cmdline: /usr/lib64/firefox-3.6/firefox -UILocale fr
component: firefox
Attached file: coredump, 189648896 bytes
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/firefox-3.6/firefox
kernel: 2.6.35.11-83.fc14.x86_64
package: firefox-3.6.15-1.fc14
rating: 4
reason: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1300207193
uid: 500

How to reproduce
-----
1. Plantage du navigateur en allant sur un site utilisant Flash après avoir installé gnash et gnash pluggin
2.
3.

Comment 1 kovaju 2011-03-16 06:32:17 UTC
Created attachment 485656 [details]
File: backtrace

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