Chris,

Thanks a lot for confirming. I think, it is very important to find the cause of it and fix it. I bet it's a problem with managers. The reference to one of them is not properly released. How can we all join our efforts of fixing the bug? Because it's causing memory leak.

>>Hi Mere Mortals users!
>>
>>Did you notice, that if you instantiate the biz object in a program, that when the object variable goes out of scope, the object's Destroy method is not fired?
>>
>>My colleague did change aBizObject, so it could be newly intoduced bug.
>>
>>Would you please test it and let me know the results?
>>
>>Thanks a lot in advance.
>
>This is what I used to test, and it confirms your observations.
>

>DO STARTMM
>DEFINE CLASS Test as kbizness of kbizness.vcx
>   PROCEDURE Destroy
>      Debugout This.Name+".Destroy()"
>      DODEFAULT()
>   ENDPROC
>
>DO Test1
>DO Test2
>
>PROCEDURE Test1
>   LOCAL oTest
>   oTest = CREATEOBJECT("Test")
>   oTest.Release()
>PROCEDURE Test2
>   LOCAL oTest
>   oTest = CREATEOBJECT("Test")
>