Bug 654345 - [abrt] seamonkey-2.0.10-1.fc14: Process /usr/lib64/seamonkey-2.0.10/seamonkey-bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] seamonkey-2.0.10-1.fc14: Process /usr/lib64/seamonkey-2.0.10/seamonkey...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: seamonkey
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:a365b874ac352afd798060a4926...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-17 16:23 UTC by Chris Schanzle
Modified: 2011-12-07 13:12 UTC (History)
3 users (show)

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


Attachments (Terms of Use)
File: backtrace (79.98 KB, text/plain)
2010-11-17 16:23 UTC, Chris Schanzle
no flags Details

Description Chris Schanzle 2010-11-17 16:23:00 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/seamonkey-2.0.10/seamonkey-bin -mail
component: seamonkey
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/seamonkey-2.0.10/seamonkey-bin
kernel: 2.6.35.6-48.fc14.x86_64
package: seamonkey-2.0.10-1.fc14
rating: 4
reason: Process /usr/lib64/seamonkey-2.0.10/seamonkey-bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1290010691
uid: 18183

How to reproduce
-----
woke system from suspend with seamonkey still running
selected message from imap server
started reply, typed about 5 words
crash

Comment 1 Chris Schanzle 2010-11-17 16:23:02 UTC
Created attachment 461102 [details]
File: backtrace

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