Re: oom-killer kicks in, how to find which process eat up memory?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Apr 22, 2009 at 1:57 PM, Jeffrey Cao <jcao.linux@xxxxxxxxx> wrote:
> Yes, I realize this. It seems that shell and its children, including my APP
> when I run it on shell, cause this problem. So, no better way than to review
> APP source code to figure out if there's memory leak. It should be a serous
> memory leak on some exception condition since that as soon as I run APP the
> oom-killer kicks in.

time to use valgrind? anyway, AFAIK, the apps that are killed by OOM
killer are not neccessarily the ones who allocate the most pages. It
is the VMA size that matters most.

regards,

Mulyadi.

--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux