wrote:
> As you should recall, you can not kill a process
> that is hung in the exit
> list. You need to figure out how to avoid this.
Sometimes easier said than done. Netscape / Mozilla
strikes me as the all-time champion for causing this,
and I find that could be the case not just on _our_
preferred platform. I've done it a couple times
lately on the Dark Side as well. Is that in the
nature of how much a browser does, and how heavily it
stresses the system ? Is it (still) much the same
"extra Hang risk" with FF or SM ?
To be fair about it, I think a plugin might be the
culprit in some of these instances . . . but I've
also seen it happen while scrolling through an
ordinary web page that was just posted forum messages.
In most cases, though, it happened in the course of
quitting the running browser. The worst is when
everything then goes unresponsive. Can't even get to
the built-in killer installed in eCS, or Task Manager
in WinBlows. I don't see this too often, but it
probably shouldn't happen at all.
Jordan
=====================================================
To unsubscribe from this list, send an email message
to "steward@scoug.com". In the body of the message,
put the command "unsubscribe scoug-help".
For problems, contact the list owner at
"postmaster@scoug.com".
=====================================================
<< Previous Message <<
>> Next Message >>
Return to [ 10 |
February |
2007 ]
The Southern California OS/2 User Group
P.O. Box 26904
Santa Ana, CA 92799-6904, USA
Copyright 2001 the Southern California OS/2 User Group. ALL RIGHTS
RESERVED.
SCOUG, Warp Expo West, and Warpfest are trademarks of the Southern California OS/2 User Group.
OS/2, Workplace Shell, and IBM are registered trademarks of International
Business Machines Corporation.
All other trademarks remain the property of their respective owners.