Beverly Howard wrote:
>> multiple Seamonkey task manager processes <<
fwiw, over the years I've become practiced at checking task manager
looking for multiple instances of seamonkey running, so, nowadays it's
rare to find more than two running at the same time, but, in the past I
have found as many as eight seamonkey processes in task manager with
only one instance of seamonkey visible on the desktop or task bar.
>> it's not "known" to me <<
I understand not having experienced this since, at this location I have
four boxes, all running XPPro which are regularly running seamonkey and
this behavior is observed on only one of the machines.
That said, I have looked at task manager on many machines at other
location and found the same thing not to mention the many posts here
asking about the same symptoms. It _appears_ to be related to some
action being taken within the email/newsreader client or the mail and
newsgroups settings, but I have been unable to manually recreate the
problem.
It is also noteworthy that this is currently happening on my primary
computer and for years, I observed the same behavior on the box it
replaced.
Fascinating. Just out of curiosity, are we talking about a machine that
runs that Quick Launch TSR (I don't)?
>> if SM is running, I /cannot/ launch a second instance <<
Note the details I have posted on this behavior... this does not happen
when seamonkey is running, nor do I use a shortcut to switch to existing
sessions of seamonkey visible on the task bar, it happens when a normal
_exit_ of seamonkey does not completely shut down and leaves seamonkey
visible in task manager long after it is exited.
In that case, the next time seamonkey is launched, that launch does not
detect the residual process that is visible in task manager and a second
task manager process, with a new pid, is launched.
In my case, when SM fails to terminate (which it does from time to
time), I can see it in the Task Manager but nowhere else and can't
interact with it, but unlike your experience, its presence /does/
prevent another instance from launching.
From my observations, once that "second" seamonkey process exists,
every shutdown of seamonkey that follows leads to another instance of
seamonkey in task manager.
>> The only reason I reboot nowadays... <<
While not as radical as your intervals, I generally reboot every two to
three weeks and use the computer as a central part of my business and
life, so, I agree, this is a factor.
I also use the computer as a central part of my business, and with all
the software I have installed, the reboot interval is often shorter than
two weeks due to updates. Just today, my Internet security software
alerted that it couldn't complete an update without a reboot, so I
performed saves and safe shutdowns of all my running applications and
allowed it to reboot.
--
War doesn't determine who's right, just who's left.
--
Paul B. Gallagher
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
