>>>please pardon me for jumping in with an unrelated question. Could this delayed garbage collection that you describe, be the reason why the "right way" to release an object, is to first set the reference to .null. and then release it? IOW, could it be that setting the reference to .null. forces VFP to do this garbage collection?
>>
>>Garbage collection is triggered on sys(1104) or
>>if vfp enters a wait state, for example a doevents or wait wind [timeout]
>>
>>Any difference in the above would only be in the set of objects waiting for the next collection.
>
>If we invoke sys(1104) in the main method of the dll, does it help? I think I tried it with no visible help, I may re-try again.

I never had the pleasure of looking for a leak across COM, so unsure.
But it might give you ideas via logging the return value -
Across COM I mostly went with resetting the WorkingSpace -
dunno if it was COM or IE.