Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Trying to track down memory leak(s)
Message
De
23/09/2011 13:47:27
 
 
Information générale
Forum:
Visual FoxPro
Catégorie:
Problèmes
Versions des environnements
Visual FoxPro:
VFP 9 SP2
Divers
Thread ID:
01398453
Message ID:
01524524
Vues:
96
>>>>>With all the small changes I made so far (restoring back calls to MySQLExec) I get 0.21 as first call and 1.77 as last call for 500 iterations.
>>>>
>>>>
>>>>The time of execution bears no relation to the memory leak imo
>>>
>>>IMHO, if execution time gradually increases for the same call with exactly same parameters - does not it indicate a memory leak?
>>
>>
>>Why should it ?
>
>Why not? How do you explain it otherwise? And also, what is the simple test to see if the memory is leaking or not?


>Why not? How do you explain it otherwise?
Lots of reasons
- the system may be busy with other (non-fox) programs/services/ etc
- it may garbage collect variables
- decrease it's memory allocation


The tests have to be run at least a couple of times to reduce influence from the above


> And also, what is the simple test to see if the memory is leaking or not?

Call the function continously - look at the memory it takes in the task manager
Gregory
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform