Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Memory Leaks
Message
De
23/07/2008 17:04:34
Jay Johengen
Altamahaw-Ossipee, Caroline du Nord, États-Unis
 
 
À
23/07/2008 16:52:20
Information générale
Forum:
Visual FoxPro
Catégorie:
Autre
Titre:
Versions des environnements
Visual FoxPro:
VFP 9 SP2
Divers
Thread ID:
01333545
Message ID:
01333557
Vues:
14
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.
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform