Bug 746515 - [abrt] seamonkey-2.0.14-1.fc14: handle_error: Process /usr/lib64/seamonkey-2.0.14/seamonkey-bin was killed by signal 6 (SIGABRT)
Summary: [abrt] seamonkey-2.0.14-1.fc14: handle_error: Process /usr/lib64/seamonkey-2....
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: seamonkey
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:466a765fe5e8fc55f63c49d835f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-16 19:18 UTC by Jaroslav Škarvada
Modified: 2011-12-07 13:07 UTC (History)
3 users (show)

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


Attachments (Terms of Use)
File: backtrace (32.90 KB, text/plain)
2011-10-16 19:18 UTC, Jaroslav Škarvada
no flags Details

Description Jaroslav Škarvada 2011-10-16 19:18:44 UTC
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 33692 bytes
cmdline: /usr/lib64/seamonkey-2.0.14/seamonkey-bin -mail
comment: It crashed shortly after close of the application window.
component: seamonkey
Attached file: coredump, 99659776 bytes
crash_function: handle_error
executable: /usr/lib64/seamonkey-2.0.14/seamonkey-bin
kernel: 2.6.35.14-97.fc14.x86_64
package: seamonkey-2.0.14-1.fc14
rating: 4
reason: Process /usr/lib64/seamonkey-2.0.14/seamonkey-bin was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1318792243
uid: 500

How to reproduce
-----
1. crashed on exit

Comment 1 Jaroslav Škarvada 2011-10-16 19:18:48 UTC
Created attachment 528413 [details]
File: backtrace

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