Closed
Bug 229281
Opened 21 years ago
Closed 19 years ago
Mozilla does not kill all threads at shut down
Categories
(SeaMonkey :: General, defect)
SeaMonkey
General
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 236768
People
(Reporter: jim.prather, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5) Gecko/20031007 Build Identifier: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.5) Gecko/20031007 I have seen several cases where mozilla failed to perform a graceful shut down and left threads running. Mozilla could not be restarted until the thread was manually killed. These were not invalid page fault crashes. It appeared that Java (1.4.2_01) crashed and then mozilla just disappeared. Reproducible: Sometimes Steps to Reproduce: 1. This is ad-hoc gorilla testing. 2. Force a Java crash, i.e. at sun.awt.font.NativeFontWrapper.registerFonts(Native Method) - locked <0x141a94c0> (a java.lang.Class) 3. Actual Results: Java crashed and logged the crash. Mozilla disappeared. Mozilla threads were still running. Could not restart mozilla. Had to manually kill mozilla. Expected Results: Graceful shut down. Mozilla can be restarted without intervention.
Comment 1•21 years ago
|
||
workaround: Upgrade to Java 1.4.2_03 http://java.sun.com/j2se/1.4.2/ Another reason for upgrade will be that the verisign certificates for older Java versions expire Jan 7th, 2004, so applets may be not allowed to connect via https: more about this here: http://forums.mozillazine.org/viewtopic.php?t=41746 and here: http://sunsolve.sun.com/pub-cgi/retrieve.pl?doc=fsalert%2F57436
Comment 2•20 years ago
|
||
There is a strong possibility that this bug, bug 254281 and bug 236540 are all DUPLICATEs of bug 236768.
Whiteboard: DUP of bug 236768
Updated•20 years ago
|
Product: Browser → Seamonkey
Comment 3•19 years ago
|
||
I am resolving this bug as a duplicate. If you can reliably reproduce the problem with the latest nightly build and while using the latest JRE version (right now, Version 1.5.0, build 1.5.0_02-b09), then reopen bug 236768. As it stands, this is a duplicate bugfile. *** This bug has been marked as a duplicate of 236768 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Whiteboard: DUP of bug 236768
You need to log in
before you can comment on or make changes to this bug.
Description
•