On Tue, Apr 21, 2009 at 07:10:17PM +0530, Vishal Thanki wrote: > Jeffrey Cao wrote: >> On 2009-04-21, Vishal Thanki <[email protected]> wrote: >> >>> Fire "top" command which will display which application is using how >>> much memory. >>> >> >> Vishal, thank you. >> But after oom-kill, the memory recovers to the normal state. >> All processes behave well. >> >> > Thats because the OOM killer may have selected the process which was > taking most of the memory. You can do one thing, run "top" in a separate > session, and then run your application in different session. > Continuously observer the "top" output, because it will reveal which > process is taking most of the time. > This bug is hard to reproduce. I've tried to test to reproduce this bug for about two weeks without any success.
-- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to [email protected] Please read the FAQ at http://kernelnewbies.org/FAQ
