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?