On Wed, Apr 22, 2009 at 03:53:50PM +0700, Mulyadi Santosa wrote: > 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. > Thank you Mulyadi. >From the dmesg, I can see that oom-killer is called several times. Shell process (including its children) is killed every time. No other processes are killed. And after this, the memory is recovered normal. So, from this I can tell It is shell and its children who cause oom trouble. Jeffrey -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
