Bug 579152

Summary: [abrt] crash in seamonkey-2.0.3-1.fc12: Process /usr/lib64/seamonkey-2.0.3/seamonkey-bin was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Dan Book <grinnz>
Component: seamonkeyAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: caillon, gecko-bugs-nobody, kengert
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:6c3866b0f07e85c9438dbfd77b35f400e008c95d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-04-02 22:01:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Dan Book 2010-04-02 21:42:15 UTC 
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/seamonkey-2.0.3/seamonkey-bin -mail
component: seamonkey
executable: /usr/lib64/seamonkey-2.0.3/seamonkey-bin
kernel: 2.6.32.10-90.fc12.x86_64
package: seamonkey-2.0.3-1.fc12
rating: 4
reason: Process /usr/lib64/seamonkey-2.0.3/seamonkey-bin was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
Comment 1 Dan Book 2010-04-02 21:42:17 UTC 
Created attachment 404240 [details]
File: backtrace
Comment 2 Kai Engert (:kaie) (inactive account) 2010-04-02 22:01:14 UTC 
Stack shows "js_GC", another one of those crashers that happen during JavaScript Garbage Collection...

I don't think we can do much about this here, the application logic must get fixed in the upstream mozilla code.

https://bugzilla.mozilla.org/show_bug.cgi?id=445204