On Friday 11 March 2005 12:53, Travis Rousseau wrote: > Why and how did it go back to normal?
most likely the program tried to allocate more memory, the kernel failed it (being exhausted) and the program crashed due to the failed malloc. some of the kernels have had OOM killers, which stop processes that seem likely to help when things go crazy. > Why didn't it crash like windows does for me when this happeneds in > windows? Linux and most other decent kernels won't die when they run out of memory to allocate to user space programs. they have a certain amount reserved for their own use, so don't become starved by such events and then try to gracefully handle the OOM condition. > and finaly What just happened? the game programmer(s) likely didn't anticipate the program being exited in the way it was, and there's likely a bug triggered by that where the program will be sitting in a loop somewhere allocating a chunk of memory each time through it. programmatic failure, in other words =) -- Aaron J. Seigo GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43
pgpMVcPoXlwew.pgp
Description: PGP signature
_______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
