Closed Bug 358295 Opened 19 years ago Closed 18 years ago

[MacOSX] SeaMonkey, with applet running, won't quit

Categories

(SeaMonkey :: General, defect)

SeaMonkey 1.0 Branch
x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: ddyer, Unassigned)

References

()

Details

(Keywords: hang, regression)

User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.0.7) Gecko/20060910 SeaMonkey/1.0.5 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.0.7) Gecko/20060910 SeaMonkey/1.0.5 seamonkey sometimes refuses to respond (or doesn't respond correctly) to a system shutdown request. I believe this problem is triggered if there is an active java applet. The referenced page has a small java applet that ticks a digital clock. Reproducible: Always Steps to Reproduce: 1. go to the referenced page 2. on your intel mac, invoke system/shutdown 3. Actual Results: after a timeout interval, the OS reports that seamonkey didn't shut down. Seamonkey is in some semi-broken state and you have to use "force quit" on it. Expected Results: Seamonkey should shut down before the system . As noted, this problem is only seen using seamonkey on an intel mac. Other browsers on the mac are fine, including mozilla and safari. Seamonkey on the pc is fine. This may be related at some level to other java-related misbehavior in seamonkey I have reported in bugs 358224 and 358292
SeaMonkey v1.0.x is not supported anymore. Can you reproduce with SeaMonkey v1.1.9 ?
Keywords: hang
Summary: seamonkey won't quit → [MacOSX] SeaMonkey, with applet running, won't quit
Version: unspecified → SeaMonkey 1.0 Branch
Could you pinpoint when it regressed ?
Keywords: regression
This problem appears to have been fixed somewhere along the way. It's no longer a problem with Seamonkey 1.1.9
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
No reference to the bug / patch that fixed the code. -> WORKSFORME
Resolution: FIXED → WORKSFORME
You need to log in before you can comment on or make changes to this bug.