Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Trying to track down memory leak(s)
Message
 
 
To
23/09/2011 11:07:38
General information
Forum:
Visual FoxPro
Category:
Troubleshooting
Environment versions
Visual FoxPro:
VFP 9 SP2
Miscellaneous
Thread ID:
01398453
Message ID:
01524494
Views:
93
>>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.
If it's not broken, fix it until it is.


My Blog
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform