Posted by PJDM on Mar 05, 2014; 12:14pm
URL: https://forum.jogamp.org/Detecting-memory-leaks-tp4031771p4031774.html

Yes, I've tried setting jogl.debug.GLBufferObjectTracker and jogl.debug.GLStatusTracker but nothing appears on stderr. Defining jogl.debug.TraceGL does produce a lot of output.

Curiously, setting jogl.verbose displays:
JOGL specification version null
JOGL implementation version null
JOGL implementation vendor null

(using 2.1.3-rc-20131212, I'm not able to use 2.1.4).

I create and delete buffers on the fly. Sometimes I might miss deleting a buffer, so that buffer leaks. Rather than scanning through the debug output, I'd like JOGL to tell me what buffers are in use. Given that JOGL seems to be tracking that information, I prefer not to have to write the code to do my own tracking as well. I want to know when I've missed candidates for the bin.

PJDM