[vtk-developers] Valgrind results for vtkGL2PSExporter

[Prabhu Ramachandran]

Hi,

Thanks to Micha Bieber and Christophe's suggestions the trouble with
fonts in the PDF output is fixed in CVS.

I wrote a test case for vtkGL2PSExporter with multi-line text and a
single cone and tested it under valgrind.  I tested all the output
formats with different sorting options etc.  I also checked one case
with Write3DPropsAsRasterImage being On.  This is possibly the one
place where memory leaks were possible.  I can't say I've tested every
possible option since there are so many.  Atleast the most used ones
have been tested.

Platform: Debian GNU/Linux stable (woody), gcc-2.95.4 20011002, VTK
off CVS (last evening), gl2ps-1.1.0.

There are no leaks as far as I can tell but there are a few warnings
that you might be interested in.  The first is in VTK:

== Use of uninitialised value of size 8
==    at 0x411D51C2: vtkFrustumCoverageCuller::Cull(vtkRenderer *, vtkProp **, int &, int &) (VTK/Rendering/vtkFrustumCoverageCuller.cxx:256)
==    by 0x412459B0: vtkRenderer::AllocateTime(void) (VTK/Rendering/vtkRenderer.cxx:404)
==    by 0x41245208: vtkRenderer::Render(void) (VTK/Rendering/vtkRenderer.cxx:227)
==    by 0x4124B465: vtkRendererCollection::Render(void) (VTK/Rendering/vtkRendererCollection.cxx:54)
== 

The above is seen even without any gl2ps related code.

Then with gl2ps:

== Conditional jump or move depends on uninitialised value(s)
==    at 0x412C0051: gl2psAddInBspImageTree (VTK/Utilities/gl2ps/gl2ps.c:1180)
==    by 0x412C0148: gl2psAddInBspImageTree (VTK/Utilities/gl2ps/gl2ps.c:1200)
==    by 0x412C0129: gl2psAddInBspImageTree (VTK/Utilities/gl2ps/gl2ps.c:1198)
==    by 0x412C024F: gl2psAddInImageTree (VTK/Utilities/gl2ps/gl2ps.c:1232)
== 


The final report on leaks with the vtkGL2PSExporter being used is this:

== LEAK SUMMARY:
==    definitely lost: 0 bytes in 0 blocks.
==    possibly lost:   0 bytes in 0 blocks.
==    still reachable: 649373 bytes in 23 blocks.
==         suppressed: 200 bytes in 1 blocks.

The "still reachable" has nothing to do with gl2ps since its there
even without the vtkGL2PSExporter being used.  So it looks like there
are no memory leaks that valgrind can detect on my platform.

I've attached the test program in case.  Note that the case with
Write3DPropsAsRasterImageOn takes a *long* while on valgrind.

cheers,
prabhu

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: TestGL2PSExporter.cxx
URL: <http://public.kitware.com/pipermail/vtk-developers/attachments/20031109/28c768fa/attachment.ksh>