[vtkusers] memory leak in vtk-6.3

[David Gobbi]

The reported leak is in the graphics driver, not in VTK itself.
It's common for graphics drivers to allocate memory for the
process and then leave the cleanup to the system.  I wouldn't
worry about it.

 - David

On Tue, Jan 12, 2016 at 4:12 PM, newcfd via vtkusers <vtkusers at vtk.org>
wrote:

> ==4393== 3,384 (56 direct, 3,328 indirect) bytes in 1 blocks are definitely
> lost in loss record 456 of 533
> ==4393==    at 0x4C2AB80: malloc (in
> /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
> ==4393==    by 0x25B987CC: ??? (in
> /usr/lib/x86_64-linux-gnu/dri/i915_dri.so)
> ==4393==    by 0x115546AC: ??? (in
> /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1.2.0)
> ==4393==    by 0x11551477: ??? (in
> /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1.2.0)
> ==4393==    by 0x115558F2: ??? (in
> /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1.2.0)
> ==4393==    by 0x1153012B: glXMakeContextCurrent (in
> /usr/lib/x86_64-linux-gnu/mesa/libGL.so.1.2.0)
> ==4393==    by 0x8A1E858: vtkXOpenGLRenderWindow::MakeCurrent()
> (vtkXOpenGLRenderWindow.cxx:1360)
> ==4393==    by 0x8A1DD4B: vtkXOpenGLRenderWindow::WindowInitialize()
> (vtkXOpenGLRenderWindow.cxx:1042)
> ==4393==    by 0x8A1DE06: vtkXOpenGLRenderWindow::Initialize()
> (vtkXOpenGLRenderWindow.cxx:1062)
> ==4393==    by 0x8A1E24C: vtkXOpenGLRenderWindow::Start()
> (vtkXOpenGLRenderWindow.cxx:1189)
> ==4393==    by 0xA73A05C: vtkRenderWindow::DoStereoRender()
> (vtkRenderWindow.cxx:748)
> ==4393==    by 0xA73A035: vtkRenderWindow::DoFDRender()
> (vtkRenderWindow.cxx:737)
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtkusers/attachments/20160112/124a835f/attachment.html>