Thanks to all who responded; Bryan Dunlap, Sean O'Connell, Sheila Hollenbaug,
Ian Mortimer, Ryan McConigley, Joe Fletcher and Peter Stern. I appreciate both
the sympathy and support;-)
Most agree the _feature_ has been around for a long time on a variety of UNIX
platforms and with a variety of Netscape releases.
Suggestions included using "ulimit" to limit cpu time or possibly use a
cron job to clobber the runaway processes.
Ryan provided some good info that I will paste in here...
I've seen similar things on just about every OS. Usually when I see it,
its something like the users exits Netscape, but at least netscape process
remains, usually chewing up a large amount of CPU power. I've never been
able to get rid of it reliably, speaking to some of my friends the general
concensis is what probably happens is its something like a popup window that
contains java that doesn't popup properly. Instead it sits in the background
trying to do something which it can't. Our guess is its some nasty java code
that gets handled properly with something like IE, but since a lot of
developers don't realise there are other browsers or OSes out there, we get
ignored. It would be interesting if you could get it down to a page that
causes the problem, then see how different machines handle the same page.
Thanks for all your help
/mark
Received on Fri Aug 17 2001 - 03:41:16 NZST