Bug 670728

Summary: [abrt] seamonkey-2.0.11-2.fc14: handle_error: Process /usr/lib64/seamonkey-2.0.11/seamonkey-bin was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Leonard J. Umina <lenumina>
Component: seamonkeyAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: caillon, gecko-bugs-nobody, kengert
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:2d0186322c58afdd646713a71545e0b28042d9d0
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-12-07 13:11:15 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

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!