Bug 669399 - [abrt] seamonkey-2.0.11-1.fc14: Process /usr/lib/seamonkey-2.0.11/seamonkey-bin was killed by signal 6 (SIGABRT)
Summary: [abrt] seamonkey-2.0.11-1.fc14: Process /usr/lib/seamonkey-2.0.11/seamonkey-b...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: seamonkey
Version: 14
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:b9e43fb89b629aab1d0ba45e406...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-13 15:14 UTC by Harley Goode
Modified: 2011-12-07 13:34 UTC (History)
3 users (show)

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

Attachments (Terms of Use)
File: backtrace (60.16 KB, text/plain)
2011-01-13 15:14 UTC, Harley Goode 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Harley Goode 2011-01-13 15:14:11 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/lib/seamonkey-2.0.11/seamonkey-bin -mail
component: seamonkey
crash_function: __cxxabiv1::__cxa_pure_virtual
executable: /usr/lib/seamonkey-2.0.11/seamonkey-bin
kernel: 2.6.35.10-74.fc14.i686.PAE
package: seamonkey-2.0.11-1.fc14
rating: 4
reason: Process /usr/lib/seamonkey-2.0.11/seamonkey-bin was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1294930467
uid: 500

How to reproduce
-----
1.Received email with link.
2.Clicked link which opened browser window.
3.Closed browser window and SeaMonkey crashed.
Comment 1 Harley Goode 2011-01-13 15:14:13 UTC 
Created attachment 473344 [details]
File: backtrace
Comment 2 Martin Stransky 2011-12-07 13:34:49 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.