Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Why does VFP get "tired"
Message
From
24/11/2004 11:35:53
 
 
To
23/11/2004 12:15:10
General information
Forum:
Visual FoxPro
Category:
Other
Environment versions
Visual FoxPro:
VFP 7 SP1
Miscellaneous
Thread ID:
00963765
Message ID:
00964354
Views:
18
>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?
Work as if you don't need money
Love as if you've never been hurt before
Live as if this is your last day to live
Dance as if no one's watching
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform