Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Memory Leaks
Message
General information
Forum:
Visual FoxPro
Category:
Other
Title:
Miscellaneous
Thread ID:
00238564
Message ID:
00239614
Views:
14
Hi Shawn,

Yes, I suspect you're on to it! Now for the hard part...

First, David Frankenbach (sp?) has something in the files here which is designed to help you find the problem. I think that it is your best first bet.

Secondly, the condition is caused by (still) having an object reference to the object which you "RELEASED". In the Developer's Guide (VFP5) or the Programmer's Guide (VFP6) checkout the section titled "Creating Object References" followed immediately by "Returning a Reference to an Object" followed immediately by "Releasing Objects and References from Memory" (the last bit has the three lines (total coverage of the issue in the docs!) that are pertinent here.

These things can be very hard to find. I hope this helps and I wish you good luck.

Cheers,

Jim N

>Jim,
>After doing some further testing I think that our "memory leaks" are being caused by an object not being entirely destroyed. You mentioned this possiblity in the previous message and I was wondering if you can expand upon it and/or give me ways to force the object to be released. Here's why I think this is the problem.
>
>Our main screen that opens with a property is a form with 8 pages on the pageframe. Each of the pages is populated by a class when the user clicks on it (though the first page is always automatically instantiated). If I open up a property on our NT machine and watch its memory usage via the taskmanager we find it taking up 10MG (fine). When I open up a second property (which will open up a second form and then use the same classes) the memory jumps to 15MG (probably b/c it doesn't open the whole libr b/c its in memory from the first property?). But when we release the second property the memory goes down to 13MF (not 10 like I expected). Is this a leak? Does foxpro open up a second version of the class for the second property or does it use the first version from the first property? If it is a leak (b/c the objects not released) is there a way to force the release (perhaps by checking for TYPE and then calling the destroy event specifically)?
>
>Thanks to you and everyone for the help
>Shawn Burke
>DRI Management Systems
Previous
Reply
Map
View

Click here to load this message in the networking platform