Jeffrey Cao wrote:
On Tue, Apr 21, 2009 at 07:10:17PM +0530, Vishal Thanki wrote:
Jeffrey Cao wrote:
On 2009-04-21, Vishal Thanki <vishalthanki@xxxxxxxxx> 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.
One thing you can try is to make sure that the problem reproduces only
when you run your app (that collect the stats). Once you are sure, you
can try to find out that if your app causes any memory leak (by looking
at source code if available). If you dont have source of that app, then
you can start your app in one session, and keep on observing the free
memory in a different session using "cat /proc/meminfo | grep -i
memfree" command.
Vishal
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ
