Bug 684421 - [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:d0ee368d7f6fac6d9f9b9115bde...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-12 12:47 UTC by Roumano
Modified: 2011-12-07 13:08 UTC (History)
1 user (show)

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


Attachments (Terms of Use)
File: backtrace (79.07 KB, text/plain)
2011-03-12 12:47 UTC, Roumano
no flags Details

Description Roumano 2011-03-12 12:47:49 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 80972 bytes
cmdline: /usr/lib64/firefox-3.6/firefox -UILocale fr
component: firefox
Attached file: coredump, 329580544 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: 1299933692
uid: 500

How to reproduce
-----
1. Upload 8 photo to my website (roumano.com) on Piwigo web site
2. After 4 or 5 pictures, firefox crash (was on background)
3.

Comment 1 Roumano 2011-03-12 12:47:53 UTC
Created attachment 483891 [details]
File: backtrace

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