Bug 683287 - [abrt] thunderbird-3.1.7-2.fc14: Process /usr/lib64/thunderbird-3.1/thunderbird-bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] thunderbird-3.1.7-2.fc14: Process /usr/lib64/thunderbird-3.1/thunderbi...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: thunderbird
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:24b3805fa9049429406fe5de27e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-09 00:58 UTC by Lancelot Mak
Modified: 2011-12-07 13:02 UTC (History)
1 user (show)

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


Attachments (Terms of Use)
File: backtrace (101.64 KB, text/plain)
2011-03-09 00:58 UTC, Lancelot Mak
no flags Details

Description Lancelot Mak 2011-03-09 00:58:03 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 104080 bytes
cmdline: /usr/lib64/thunderbird-3.1/thunderbird-bin
component: thunderbird
Attached file: coredump, 329920512 bytes
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/thunderbird-3.1/thunderbird-bin
kernel: 2.6.35.11-83.fc14.x86_64
package: thunderbird-3.1.7-2.fc14
rating: 4
reason: Process /usr/lib64/thunderbird-3.1/thunderbird-bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1299632006
uid: 500

How to reproduce
-----
1.
2.
3.
just scrolling mouse down

Comment 1 Lancelot Mak 2011-03-09 00:58:06 UTC
Created attachment 483081 [details]
File: backtrace

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