|
I am trying to debug a program which constantly
grows in memory use from ~1.9GB to 2.7GB (on Linux) and crashes due to out of
memory. I found that memprof might be able to give profile information during
the run and pinpoint which portion is contributing to the memory growth (since
there are 4 different vendor tools linked into the binary).
On a smaller testcase (of very similar nature)
memprof works fine and gives profiling output which can be saved to a file and
post-processed. But when being used on the full testcase, it itself starts
consuming more memory and crashes when it hits 2.7GB linux limit.
Has anyone seen this sort of behavior before? Any
way to, say, tell memprof that it doesn't need to profile certain
functions (which might reduce the amount of information it has to analyze)?
I am using 0.4.1 version of memprof.
Thanks in advance,
Maulik
|