Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Why does VFP get "tired"
Message
From
24/11/2004 12:51:11
 
 
To
24/11/2004 11:35:53
General information
Forum:
Visual FoxPro
Category:
Other
Environment versions
Visual FoxPro:
VFP 7 SP1
Miscellaneous
Thread ID:
00963765
Message ID:
00964392
Views:
14
>>A "dangling object reference" is a memvar reference to some part of *another* object. Such a reference prevents that actual freeing of the referencED object, EVEN IF YOU EXPLICITLY ISSUE A RELEASE command! In such a case the actual object reference memvar does indeed disappear BUT the object itself remains in memory. A simple sample:
oX = CREATEOBJECT("MyForm")
>>RefPage2 = oX.Pgf.P2
>>    *
>>    *
>>   lots of code
>>RELEASE oX
The actual memvar reference "oX" will disappear, but the object "oX" will remain in storage because "RefPage2" holds a reference to an object within the oX object.
>>Now imagine repeating that code over and over again. Soon enough you'll have multiple extraneous copies of object "oX" residng in memory.
>>
>
>Hi Jim.
>Would
>
>oX = NULL
>RELEASE oX
>
>Solve this?

Don't think so... don't really see any difference because the "RefPage2" object reference still exists.
But I'll try it out when Ihave the time.

cheers
Previous
Reply
Map
View

Click here to load this message in the networking platform