Heap memory keeps increasing until Snapshot is taken

Memory profiling for .NET developers

Heap memory keeps increasing until Snapshot is taken

Postby Houman » Thu Sep 29, 2011 5:18 pm

Hi,

We are a new customer of Memory Profiler 7.1.

We have a WPF application that keeps growing memory in the Windows Task manager, hence we purchased this profiler to see how it can help us.

Whenever we start clicking on different tabs on the main screen the data gets populated into the new tabs hence the memory usage increases. The memory profiler shows a natural increase in memory, which we expect. I call the memory usage state after this natural increase in memory simply for convenience of the discussion here the "initial state".

After a while of inactivity though, I can see that the heap memory and the Large Heap Size keep increasing for no reason.

However in the moment I take a new memory Snapshot so see what's happening, both the heap memory and the large object heap size go down to the "initial state". This makes the point of having the profiler a bit pointless.

What makes the "initial state" go up at all despite the inactivity?

Many Thanks

Image
Houman
 
Posts: 2
Joined: Thu Sep 29, 2011 4:58 pm

Postby Houman » Fri Sep 30, 2011 9:28 am

Hi,

I have been running the app over the night and can see that the memory is freed up after exactly 2 hours and 15 minutes.

Any advice?


Image
Houman
 
Posts: 2
Joined: Thu Sep 29, 2011 4:58 pm

Postby Brian Donahue » Mon Oct 03, 2011 10:24 am

It doesn't look like you have a memory leak. It's getting freed up, eventually.
Brian Donahue
 
Posts: 6670
Joined: Mon Aug 23, 2004 10:48 am


Return to ANTS Memory Profiler 7

Who is online

Users browsing this forum: No registered users and 0 guests