Bug 729192 - [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:ccbe99ee3b89da687fee338fe8b...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-09 02:20 UTC by Kevin Tough
Modified: 2011-12-07 13:19 UTC (History)
3 users (show)

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

Attachments (Terms of Use)
File: backtrace (53.70 KB, text/plain)
2011-08-09 02:20 UTC, Kevin Tough 		no flags Details
View All

Description Kevin Tough 2011-08-09 02:20:54 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 54990 bytes
cmdline: /usr/lib64/seamonkey-2.0.14/seamonkey-bin
comment: Check the site if it's name is listed in the trace.
component: seamonkey
Attached file: coredump, 180891648 bytes
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib64/seamonkey-2.0.14/seamonkey-bin
kernel: 2.6.35.13-92.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 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1312855448
uid: 500

How to reproduce
-----
1.Tried to open a new site...
2.
3.
Comment 1 Kevin Tough 2011-08-09 02:20:57 UTC 
Created attachment 517333 [details]
File: backtrace
Comment 2 Martin Stransky 2011-12-07 13:19:48 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.