[IGSTK-Developers] VTK_DEBUG_LEAKS option

[David Gobbi]

Thanks for the hint, this highlighted a bit of code that wasn't deleting
a igstkVTKLoggerOutput object.

The VTK-derived classes in IGSTK (View, VTKLoggerOutput)
don't have smart pointer typedefs, which make them succeptible to
leaks like this.  It's easy to remedy, though, because we can add
vtkSmartPointer typedefs to these classes as follows:

    typedef vtkSmartPointer<Self>          Pointer;
    typedef vtkSmartPointer<const Self> ConstPointer;

I've already done this for VTKLoggerOutput.  I'll do the same
for the View classes.

Andinet Enquobahrie wrote:

> To developers who are adminstrating the machines on the IGSTK dashboard,
>
> Please turn on the VTK_DEBUG_LEAKS option in your VTK build..  This 
> option is useful to detect memory leak problems in the vtk dependent 
> IGSTK classes.
>
> thanks,
> -Andinet
>
> _______________________________________________
> IGSTK-Developers mailing list
> IGSTK-Developers at public.kitware.com
> http://public.kitware.com/cgi-bin/mailman/listinfo/igstk-developers
>