Rick Merrill wrote:
Paul B. Gallagher wrote:
Leonidas Jones wrote:
<u...@domain.invalid> wrote:
Running SeaMonkey 2.0.8 under Windows XP SP3 (long time SM
user). When I exit SeaMonkey by closing all the windows or
using the Exit menu item), the Seamonkey process continues to
run invisibly and consumes about 1/2 of the CPU to no
worthwhile effect that I can see. I terminate this errant
process with Task Manager.
It's probably not a good idea to do that.
When SeaMonkey closes down, it writes changes to it's
configuration files, such as prefs.js and others. By aborting
this early, you are not allowing it to complete these cleanup
tasks.
I have a similar experience (SM sometimes fails to terminate
properly), and I have sometimes waited 10 minutes or more while it
does nothing (consumes 0% of my CPU) before forcing it to close.
The program has always run fine afterward. I have never seen it
terminate on its own once it reaches this state.
By "this state" I mean:
• program is visible only in Task Manager;
• program is consuming 0% of CPU and has been for at least two minutes.
I have not yet identified any user actions that can reliably cause
this fault, and I've been looking since I first noticed it in
Mozilla 1.7.
I've seen that happen and I attribute it to "empty trash on exit" -
that's at least a possibility.
This "running on" can also interfere with re-launching SeaMonkey, BUT
they have now fixed it so that instead of creating multiple copies
of SM it waits.
Yes, that's my experience, too. If I try to launch SM while this is
going on, nothing happens. And that's usually my tip-off to check Task
Manager. Once I force the hung instance to close, I'm then free to
launch it again and run normally.
--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher
_______________________________________________
support-seamonkey mailing list
support-seamonkey@lists.mozilla.org
https://lists.mozilla.org/listinfo/support-seamonkey
