On Tue, Apr 21, 2009 at 02:50:47PM +0100, Srdjan Todorovic wrote: > Hi, > > 2009/4/21 Jeffrey Cao <[email protected]>: > > > Out of Memory: Kill process 429 (sh) score 297 and children. > > Out of memory: Killed process 429 (sh). > > > How to find out which process eat up the memory? Any clues? > > Your shell seems to have caused the OOM killer to do its work... > 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.
-- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to [email protected] Please read the FAQ at http://kernelnewbies.org/FAQ
