Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Memory Leaks
Message
From
23/07/2008 17:04:34
Jay Johengen
Altamahaw-Ossipee, North Carolina, United States
 
 
To
23/07/2008 16:52:20
General information
Forum:
Visual FoxPro
Category:
Other
Title:
Environment versions
Visual FoxPro:
VFP 9 SP2
Miscellaneous
Thread ID:
01333545
Message ID:
01333557
Views:
15
No memo fields and we can watch the used memory grow as it is running. I asked in the other thread, but why is the RETURN a bad thing in the WITH/ENDWITH?

Update: And does that mean any type of RETURN, like this?
RETURN CHRTRAN( InputText, CharsToStrip, '')
>You sure it's a memory leak? I've seen issue when using memo fields alot. Also make sure you don't have a RETURN inside a WITH/ENDWITH.
>
>>What are the first places to look for memory leaks in code? We have something that runs a process and the longer it runs (more records) then the memory keeps growing until all the available is chewed up and it crashes and burns.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform