[lkml]   [2007]   [Jun]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Runaway process and oom-killer
John Sigler wrote:
> Andrea Arcangeli wrote:
>> On Wed, Jun 13, 2007 at 10:49:29AM +0200, John Sigler wrote:
>>> Question 2: how can I tell which process or kernel thread was
>>> hogging most of the RAM when the oom-killer kicked in?
>> Theoretically the one that was killed first but not for sure in
>> current mainline hence see below.
> If I read the logs correctly, oom-killer is "invoked" three times
> before it effectively kills a process. Then oom-killer kills myapp,
> syslogd, and boa, in that order. Why didn't oom-killer kill anything
> the first three times?
My guess:
Something needs memory but finds there is none to be had
oom-killer is invoked and targets myapp.
myapp takes some time to die. Particularly, the memory it uses
isn't freed up instantly. In the meantime something else
needs memory and find none. (Another packet received?)
The oom-killer is invoked again, this time it targets syslogd.

And so on. The kernel do many things in parallel, running out
of memory in a multitasking system therefore is a complicated business.
Especially when process killing takes some time.

Note that you can turn off memory overcommit, your leaky app
should then get a memory allocation error instead of
triggering the oom-killer.

Helge Hafting

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2007-06-13 15:45    [W:0.094 / U:8.784 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site