[vtkusers] VTK not releasing memory, including minimal example.

David Gobbi david.gobbi at gmail.com
Mon Sep 24 16:43:17 EDT 2012

The only thing that SetActiveCamera() does in this case is cause the
renderer to not automatically call ResetCamera() on the first render.

If you replace this line:


with this line:


does it give exactly the same memory usage?  Either of these will
eliminate the automatic call to ResetCamera().

Also, with your valgrind run from a couple messages ago, it looks like
you just ran "valgrind" without running "valgrind --leak-check=full"
as I had recommended.  Without the "--leak-check=full", valgrind will
not tell you where the leaked memory was allocated, and that's what we
really want to know.  We want to know if the memory was allocated in
the graphics drivers, in the X11 libraries, or if was allocated in one
of the VTK libraries.

 - David

On Mon, Sep 24, 2012 at 2:06 PM, P.J.Schaafsma
<jetze.schaafsma at gmail.com> wrote:
> Ok, here's the deal. It's a bug in VTK.
> If you do a renderer.SetActiveCamera(vtk.vtkCamera()) before the first
> Render() call, all is well. If you don't, memory is being hogged.
> Don't know why the issue didn't arise on my other machine.

More information about the vtkusers mailing list