Tomas Hnilica wrote:
I tried to find the problem with valgrind on Linux, but it reports loss
of memory in the OSG code, what is probably wrong interpretation. Does
anynone use valgrind for memory leak detection in OSG apps or can you
recommend other method?
Did you compile your code with debug info? It's hard to tell where the
leak might be occurring, because the stack trace doesn't go back far enough:
==11693== by 0x5EFA072: osgFX::Effect::Effect() (in
/home/tomas/OpenSceneGraph-2.8.0/lib/libosgFX.so.2.8.0)
==11693== by 0x5EFCDDF: osgFX::Scribe::Scribe() (in
/home/tomas/OpenSceneGraph-2.8.0/lib/libosgFX.so.2.8.0)
==11693== by 0x2989BE06: ???
OSG does use ref_ptr's to help keep leaks from happening, but that
assumes that you're using them correctly in your program as well :-)
Also, Simplifier and osgFX::Effect aren't used as much as other parts of
the libraries (at least I wouldn't expect that they are), so it's
possible those sections aren't 100% leak-free. It's conceivable that
you're the first person to exercise them enough to bring up a latent
problem there.
--"J"
_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
