>>>>I'm looking for ideas on tracking down memory leaks in an application. Here's the background. I have a VFP EXE (call it UI) that instantiates a VFP COM DLL (call it DL). DL instantiates another VFP COM DLL (call it Online Timer) and a C# DLL (call it Comms). Comms talks to some hardware.
>>>>
>>>
>>>Are you instanciating the .NET COM component a lot or are you just holding a reference to it? Do you know if the memory is being taken by VFP or by one of your COM components? You could probably test whether it's happening in .NET pretty easily by creating a dummy/stub version of it then monitoring the memory usage.
>>>
>>>Are you explicitly releasing the variables (or properties) in DL that access your UI?
>>
>>First, this is a good place for me to correct one mistake in my original message. The VFP COM objects are EXE, not DLL (because I need timers to work in them).
>>
>>We instantiate the .NET object once at start-up. Ditto for the VFP COM objects. It's the main VFP EXE that's ballooning.
>>
>>Yes, I'm cleaning up all the back and forward references on the way out.
>>
>
>Does the memory come back if you release and reinstanciate the VFP COM objects?

I don't know and that would be extremely hard to test in this app. What I have been testing today (left running the last 3 hours to get some real data) is what happens if I run with those objects built in instead of COM.

Tamar