>>>>>>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

In my other thread that has 0 answers I posted the procedure I'm trying. I'm running calling the same method in a loop of 500 iterations. I ran 20+ tests yesterday and couple today - I always got the same result - the execution time of each call gradually increases.
The clients experience exactly the same problem, so they have been restarting this dll after ~30 minutes of work.