Bug 641548

Summary: [abrt] seamonkey-2.0.8-1.fc13: Process /usr/lib/seamonkey-2.0.8/seamonkey-bin was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Michael Gruys <m.gruys>
Component: seamonkeyAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: aggibson, arang1978, caillon, dewero, gecko-bugs-nobody, ghosler, kengert, lenumina, shill, skeeter1029
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:cb05b6c8997004daa1af23c18fc99be8eaedfaf1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-28 11:48:32 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
Crash Reporter add-on "report" none

Description Michael Gruys 2010-10-09 07:24:57 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: /usr/lib/seamonkey-2.0.8/seamonkey-bin
component: seamonkey
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/lib/seamonkey-2.0.8/seamonkey-bin
kernel: 2.6.34.7-56.fc13.i686.PAE
package: seamonkey-2.0.8-1.fc13
rating: 4
reason: Process /usr/lib/seamonkey-2.0.8/seamonkey-bin was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1286608417
uid: 500

How to reproduce
-----
1.Start Seamonkey
2.Execute the Cookie Manager
3.Choose the Cookie Sites tab
4. Press the Help button

Comment 1 Michael Gruys 2010-10-09 07:25:01 UTC
Created attachment 452479 [details]
File: backtrace

Comment 2 Greg Hosler 2010-10-10 05:28:56 UTC
Package: seamonkey-2.0.8-1.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. Open multiple tabs with right click on url
2. within newly opened page, save a file (right click save url)
3. close tab.


Comment
-----
This appears to be some sort of race condition. It does not always happen. Usually doesn't crash.
Maybe 10% of the time it will crash.

However, I do this often enough that a crash usually will happen within one session of opening
up pages, saving urls.

BUT ...

When I close the last tabe (the main uI, by clicking on the [x] in the upper right of the UI),
*MOST* of the time it will generate a crash. Maybe 90% of the time it will generate a crash.

Comment 3 Drew 2010-10-12 03:27:03 UTC
Package: seamonkey-2.0.8-1.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. Used Seamonkey
2.Closed Seamonkey
3. Crashed similar to .06


Comment
-----
First crash since update to .08, used to be every time

Comment 4 dedanna 2010-10-16 02:13:57 UTC
Package: seamonkey-2.0.8-1.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. Seamonkey crashed out of the middle of nowhere on my Facebook page.
2. I do not know specifically what caused this.
3. This is now a long-standing issue with Seamonkey


Comment
-----
Closed out a couple tabs in Seamonkey, was on my Facebook page, and it crashed.

This is very old and tired now.

Comment 5 dedanna 2010-10-16 03:07:22 UTC
Created attachment 453831 [details]
Crash Reporter add-on "report"

From Seamonkey's own Crash Reporter - when I reloaded it from this last time it crashed, this is what came up. Although, I wasn't on a flash page when it crashed. :P

Comment 6 Leonard J. Umina 2010-10-17 05:55:56 UTC
Package: seamonkey-2.0.8-1.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1.
2.
3.
trying to configure a samba share

Comment 7 Mason 2010-10-24 21:28:22 UTC
seamonkey-2.0.8-2 is supposed to fix this bug.
Please see bug 602437.

seamonkey-2.0.9-1 will be available in a few days.
http://koji.fedoraproject.org/koji/packageinfo?packageID=3814

Comment 8 Bug Zapper 2011-05-31 11:41:16 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 9 Bug Zapper 2011-06-28 11:48:32 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.