Bug 683555 - [abrt] firefox-3.6.14-1.fc14: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
Summary: [abrt] firefox-3.6.14-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:d229c9a3c4b6cf70e88c1df24a8...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-09 17:21 UTC by David W. Legg
Modified: 2011-12-07 13:24 UTC (History)
1 user (show)

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


Attachments (Terms of Use)
File: backtrace (64.18 KB, text/plain)
2011-03-09 17:21 UTC, David W. Legg
no flags Details

Description David W. Legg 2011-03-09 17:21:01 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 65716 bytes
cmdline: /usr/lib64/firefox-3.6/firefox -UILocale en-GB
comment: As above.
component: firefox
Attached file: coredump, 338362368 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.14-1.fc14
rating: 4
reason: Process /usr/lib64/firefox-3.6/firefox was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1299690573
uid: 504

How to reproduce
-----
1. Used Firefox on eBay.
2. Closed it with x in top right hand corner under KDE 4.
3. Crash

Comment 1 David W. Legg 2011-03-09 17:21:04 UTC
Created attachment 483267 [details]
File: backtrace

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