Bug 670728 - [abrt] seamonkey-2.0.11-2.fc14: handle_error: Process /usr/lib64/seamonkey-2.0.11/seamonkey-bin was killed by signal 6 (SIGABRT)
Summary: [abrt] seamonkey-2.0.11-2.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
low
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:2d0186322c58afdd646713a7154...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-19 05:35 UTC by Leonard J. Umina
Modified: 2011-12-07 13:11 UTC (History)
3 users (show)

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

Attachments (Terms of Use)
File: backtrace (30.68 KB, text/plain)
2011-01-19 05:35 UTC, Leonard J. Umina 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Leonard J. Umina 2011-01-19 05:35:14 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/seamonkey-2.0.11/seamonkey-bin
component: seamonkey
crash_function: handle_error
executable: /usr/lib64/seamonkey-2.0.11/seamonkey-bin
kernel: 2.6.35.10-74.fc14.x86_64
package: seamonkey-2.0.11-2.fc14
rating: 4
reason: Process /usr/lib64/seamonkey-2.0.11/seamonkey-bin was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1294990284
uid: 500

How to reproduce
-----
1. on uc davis website 
2. sent email on gmail
3.
Comment 1 Leonard J. Umina 2011-01-19 05:35:17 UTC 
Created attachment 474193 [details]
File: backtrace
Comment 2 Leonard J. Umina 2011-01-19 05:40:09 UTC 
Package: seamonkey-2.0.11-2.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.closing browser after running gmail
2.
3.
Comment 3 Martin Stransky 2011-12-07 13:11:15 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.