Hi Gregory,

>I wonder - how do you mesure the 'leak' ? ie how do you know there's a leak ?

Thanks for dropping in. Looks like there is some sort of "incrédulité", disbelief when one does challenge the good ol' VFP code base. Not the first time. I have no problem with this:-)

The code in this segment of the _system.vcx library is IMHO not perfect. It is certainly not on par with the executable VFP C++ code base and partly feels like an unfinished hack. You just need to read the code to grasp this. Yousfi found an error. I did as well found a few dubious lines in it. Yep, hacks are useful but finding leaks in them is just plain routine.

Measure the leak ? As I always did in my last 30 years of fox, - been a user of fox since foxbase in 1984 or 195 if my memory serves me well .... - with the support of system level memory consumption monitoring tools. In this recent case the "window task manager".

As from my local "gestionnaire de taches Windows" the memory use increases with this code calls - and not the one provided by Anatolij by the way. I rarely bump into VFP memory leaks. But when I do, I report them here. Not to the MS-fox team -:) Not the first time I do.

It feels like a mem leak. I may be wrong of course or W10 related or even workstation dependant.But well If it looks like a duck, swims like a duck, and quacks like a duck, then it probably is a...Duck.

Daniel