🚀 go-pugleaf

I have a very large client application that appears to have a memory 
leak under certain conditions. The symptom is that Windows Task Manager 
reports increasingly high MemoryUsage over the course of several days to 
the point where the machine becomes sluggish or the application shuts 
down.

I tried to use GetHeapStatus() to track local memory allocation along 
with my calls to NEW and DELETE, but it doesn't agree with the Task 
Manager.  Specifically, THeapStatus.TotalAllocated stays the same 
(around 36M) once it settles down but TM MemoryUsage continues to climb.

I'm assuming that anything I do programatically, such as create new 
forms, allocate blocks of memory, etc, all will be reflected in 
GetHeapStatus().  If this is not the case, I need some way to meter how 
much memory I'm consuming.

I've also noticed that Task Manager will report large Memory Usage (say 
80 M) that will drop to 1-2M when the application is minimized, but when 
I refocus, Memory Usage doesn't return to 80M - it goes to some moderate 
value in between (15M or so).  I don't know if this behavior is telling 
me that TM Memory Usage is unreliable, or if I have some coding problem 
that contributes to this.

So:

1. Is Task Manager Memory Usage reliable?
2. Is GetHeapStatus() reliable, and if so, why doesn't it agree with TM?
3. Are there other tools to analyze my application's memory usage 
dynamically? For all I know, this could be a handle leak or something in 
my forms management that is at fault.

thanks for any ideas.

Mike