At 7:53 PM +0700 10/28/05, Strong wrote: >I have FC4 on Celereon 2,4 512RAM, Seagate 120*10^9 bytes. >I was writing a letter in Evolution when my system started to behave as >if it was extremaly loaded (it was almost impossible to move mouse >arrow). I noticed hdd-activity, then it ceased, still no application was >working. At that moment I ran several terminals doing nothing, >Evolution, Kate. >That's what I found in /var/log/messages after I did reload it (it gave >such a possibility): > >19:35:25 kernel: oom-killer: gfp_mask=0x1d2 ... >19:35:43 kernel: Out of Memory: Killed process 1558 (klauncher). >19:35:43 kernel: oom-killer: gfp_mask=0x1d2 ... >I never saw such records in the messages as well as never experienced >such a problem. Can anybody explain it? Can I do something to prevent it >for the next time?! Thank You! It's the (standard *nix) Out Of Memory Killer, that kills whatever task is running when the computer runs out of memory. Usually the running task is the offending task, but if not, usually a few tries are enough to get the right one. I grant you that it's a sloppy way to work. The second time you show the line that says klauncher was running, but you don't show the previous time, or perhaps many previous times. Look farther up in the log and see what's there. If that doesn't help, and it happens again, try having top running to see who's using the memory. Top can sort on the memory use; normally just type a ">" once and you'll see the list sorted by %mem. ____________________________________________________________________ TonyN.:' <mailto:tonynelson@xxxxxxxxxxxxxxxxx> ' <http://www.georgeanelson.com/>
