Posted by seb on Oct 25, 2011; 7:26am
URL: https://forum.jogamp.org/JOGL-current-application-consumes-more-and-more-memory-tp3448015p3450708.html

thank you for your quick reply,

I will try to run my application against the suggested build first and report the result here.

my question was more whether there is anything to do to convince myself that the bug is on our side (we have spent the last 10 days auditing our code (relatively small i.e. 2000 lines but part of a much much bigger application we do not control) and doing all sorts of checks.

Is there anything we can do to trace memory allocations from the native code ? Ideally I would love a trace of all mallocs done by the JNI component ? I was looking for a way to LD_PRELOAD a malloc library but I do not want to see the mallocs of the JVM ? I guess I could recompile jogl to do this but I was wondering whether anything like this is already done ?