The description and the problem are consistent with XPs behavior when
a process uses gobs and gobs of memory, sending XP into a terrible
swapping-loop.
Just as a note, given some of the comments in this thread: I'm a major Linux fan, but honestly, the same thing happens under Linux when an app consumes monstrous amounts of memory -- it doesn't bring the whole system to a halt, but it does bring X pretty much to its knees, which is almost the same thing to most people these days.
-Chris
···
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
True. I was taking the OP's word for it that CPU usage was the
problem. If the application is using so much memory that the
sysmtem can't cope, then the application probably needs to be
fixed.
···
On 2008-01-17, Christopher Barker <Chris.Barker@noaa.gov> wrote:
Chris Mellon wrote:
The description and the problem are consistent with XPs behavior when
a process uses gobs and gobs of memory, sending XP into a terrible
swapping-loop.
Just as a note, given some of the comments in this thread: I'm a major
Linux fan, but honestly, the same thing happens under Linux when an app
consumes monstrous amounts of memory -- it doesn't bring the whole
system to a halt, but it does bring X pretty much to its knees, which is
almost the same thing to most people these days.
--
Grant Edwards grante Yow! I guess you guys got
at BIG MUSCLES from doing too
visi.com much STUDYING!