Bug 736755 - [abrt] seamonkey-2.0.14-1.fc14: Process /usr/lib64/seamonkey-2.0.14/seamonkey-bin was killed by signal 11 (SIGSEGV)
Summary: [abrt] seamonkey-2.0.14-1.fc14: Process /usr/lib64/seamonkey-2.0.14/seamonkey...
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:5d5ebdc69c4955d1f8ccb4f0d0d...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-08 15:52 UTC by John Selmys
Modified: 2011-12-07 13:28 UTC (History)
3 users (show)

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


Attachments (Terms of Use)
File: backtrace (106.49 KB, text/plain)
2011-09-08 15:52 UTC, John Selmys
no flags Details

Description John Selmys 2011-09-08 15:52:46 UTC
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 109041 bytes
cmdline: /usr/lib64/seamonkey-2.0.14/seamonkey-bin
comment: crashes at random times
component: seamonkey
Attached file: coredump, 375185408 bytes
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/seamonkey-2.0.14/seamonkey-bin
kernel: 2.6.35.14-96.fc14.x86_64
package: seamonkey-2.0.14-1.fc14
rating: 3
reason: Process /usr/lib64/seamonkey-2.0.14/seamonkey-bin was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1315497002
uid: 500

How to reproduce
-----
1. start seamonkey
2. browse a while
3. crash

Comment 1 John Selmys 2011-09-08 15:52:50 UTC
Created attachment 522151 [details]
File: backtrace

Comment 2 Martin Stransky 2011-12-07 13:28:08 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@redhat.com).

Thanks!


Note You need to log in before you can comment on or make changes to this bug.