Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
VFP 6.0 sp3: Memory leak bug is back on faster machine
Message
From
21/07/2000 13:24:25
 
 
To
All
General information
Forum:
Visual FoxPro
Category:
Troubleshooting
Title:
VFP 6.0 sp3: Memory leak bug is back on faster machine
Miscellaneous
Thread ID:
00395568
Message ID:
00395568
Views:
50
Hello all,

Quite some time ago I had a problem where small jobs would run on a machine under a VFP automation server (.exe) but larger jobs would fail due to memory leaks. We started running the larger jobs in the VFP development environment and that solved some of the problem. But REALLY BIG jobs would still fail with c..5 errors or other weird memory errors, "property XXX not found" where XXX was a field in the currently selected alias, etc.

The latter were resolved by taking some SQL code that was being called reiteratively w/in a SCAN (or DO WHILE) and rewriting it in procedural code. We also put some WAIT WINDOW '' TIMEOUT 1 commands for every 100 iterations of the loop which also helped let things "catch up". However, we are not yet "100% SQL Free" in this job. Memory leaks have been proven by benchmarking performance degradation directly related to job size AND continuously increasing memory usage as the procedure runs. Variables are being explicitly released, we have FLUSH in various parts of the code. Many, many hours have gone into this problem.

All has been well for nearly a year, until one client upgraded to a much faster machine. They went from a dual PII350 to a dual PIII450. The OS changed from NT Server 4.0 to W2K Advanced Server. Both machines have 512MB RAM. We have other places running this stuff under W2K AS but not this big of a job.. Anyway, I think its the faster CPU that is making things "worse".

The following snapshot of the debugger is the proof. The error was "property keymember not found" and yet the currently selected alias is the same alias being referenced, the field(2) function returns the "keymember" field name. Note that at this point in the code execution this same line of code has already been executed perhaps 10,000 times by the calling procedure (once for each record of a cursor).

http://www.e-z.net/~spartacs/images/PROOFOFBUG.gif

Any ideas would be greatly appreciated. I will be installing VFP sp4 but I'm not getting my hopes up. Does anyone know for sure if any memory leak problems have been solved under SP4??

Thanks!!!

========================================
Christian Berrigan
Voice: 360-546-1304
E-Fax: 360-397-0174
Next
Reply
Map
View

Click here to load this message in the networking platform