This project has moved and is read-only. For the latest updates, please go here.

Leak detection using VLD for large applications - storing of internal allocations tables on disk?

Oct 6, 2016 at 10:14 AM
first thank you for this great tool, I've been using it in various companies over the years!

I am really curious what approaches (VLD as well as non-VLD) developers use to perform a full leak detection for a large application, which typically runs on continuous integration machines.
On such CI machines, there aren't unfortunately tens of GB of RAM to profile an application using VLD (due to the memory blocks being allocated by the VLD tool).
However, there is certainly enough disk space, if VLD would allow to store (a big part or all of) its internal allocation tables on disk. I certainly understand that this will make the overall detection slower, but this is not a show-stopper for such use-cases.

Was/is such a feature available / considered in current/future VLD versions?
Would you find it beneficial?

Oct 7, 2016 at 8:32 PM
I've tested performance and robustness of my own memory leak detection tool -

I think it can handle large amount of allocations with relatively good performance.

It eats some memory, but nothing dramatic compared for example to other tools.