Closed Bug 351976 Opened 18 years ago Closed 18 years ago

Seamonkey keeps running in Task Manager when all windows are closed

Categories

(SeaMonkey :: General, defect)

Product:
SeaMonkey
Component:
General
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: smedleys, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060909 SeaMonkey/1.5a
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060909 SeaMonkey/1.5a

A copy of Seamonkey stays running in the Windows Task Manager after all Browser windows are closed. 

Reproducible: Always

Steps to Reproduce:
1.  Close all instance of Seamonkey 
2.  Check Task Manager there will be a Seamonkey in ther
3.



Expected Results:  
There should not be any stub of Seamonkey running after all windows are closed
Did this also occour with older builds or only recently? Does this also happen with a new profile?
Thanks for suggesting to try a new profile.  I have never previously set profiles different than the default.  It appears to work OK with a new profile.  I will clear the Default profile and recreate it and see what happens.
Summary: Seamonkey keeps running in Task MAnager when all instances closed → Seamonkey keeps running in Task Manager when all windows are closed
I have tried deleting and recreating the Default User and the error returns when I use that profile.  Do I need to do more than use the Profile Manager to do this change more effectively?
Dumb question here, but do you use Quick Launch?  
No I do not use Quick Launch.

I appear to have resolved the problem.  To current Default user profiles seemed to be "corrupted".  To clear this I had to create a new profile and then delete the Default user profile and rename the new one I created to call it Default user.  I was not able to just delete the profile and recreate it. 

This bug and 351976 and 351974 seems to have all been related to a corrupt profile.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
*** Bug 351972 has been marked as a duplicate of this bug. ***
*** Bug 351974 has been marked as a duplicate of this bug. ***
Nothing broken or fixed in the code.

-> WORKSFORME
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago → 18 years ago
Resolution: --- → WORKSFORME
In my case high amount of cpu-usage by in task manager still running seamonkey.exe (version 1.1b).
You need to log in before you can comment on or make changes to this bug.