which method/tool is best to check memory leak for VTK programs on Ubuntu? vtkDebugLeaks enough? or Valgrind/ASan?

[gpu]

which method/tool is best to check memory leak for VTK programs on Ubuntu? vtkDebugLeaks enough? or Valgrind/ASan?
thanks

[mwestphal (Mathieu Westphal (Kitware))]

VTK_DEBUG_LEAKS

New feature: getting a stack trace on leaked objects with VTK_DEBUG_LEAKS

I just merged a new feature to VTK that augments vtkDebugLeaks. This feature lets you record a stack trace where leaked VTK objects were allocated. This can be a very useful when debugging VTK object leaks. Previously, if you configured VTK with VTK_DEBUG_LEAKS set to ON, VTK would report the types of VTK objects that were never deleted and how many there were when the application exited. This was a useful feature to let you know there was a leak, but it didn’t provide much insight into where t…

[gpu]

thanks!
may i ask it’s added since which version of VTK?
using it is enough to detect memory leaks, as Valgrind and ASan?

[mwestphal (Mathieu Westphal (Kitware))]

VTK_DEBUG_LEAKS is old, while the link I shared is only present in VTK 9.

Valgrind and Asan will find more potential leaks but will have a lot of false positive as they rely on monitoring the memory directly (kindof).

VTK _DEBUG_LEAKS will find all vtkObject that are not correct deallocated.

[gpu]

thanks, also find VTK_DEBUG_LEAKS in vtk-8.1, so what’s ur suggestion on Ubuntu? just use VTK_DEBUG_LEAKS? or maybe combine it with valgrind or ASan? or just use ASan/valgrind?
the project has some custom derived class from vtk class

[mwestphal (Mathieu Westphal (Kitware))]

If you have a suspicion for a leak, enable VTK_DEBUG_LEAKS, if nothing comes up, use valgrind.