Posted by gouessej on Jan 01, 2011; 3:29pm
URL: https://forum.jogamp.org/high-memory-consumption-in-JOGL-tp2141331p2176198.html

Hi!

I ported a viewer from JOGL 1.1.1 to JOGL 2. This viewer is used to display simple meshes that use a few static VBOs. The switch to JOGL 2.0 has significantly increased the memory consumption and jvisualvm shows that a lot of StructAccessor instances are used even for the same direct nio buffers which is completely useless.

AWT is no more the primary target but using GLCanvas is easier to port existing 3D engines to JOGL 2. I will never convince Josh to switch to JOGL 2 with such an high memory consumption. Of course, I will investigate by myself but let me know any information about this class.

Edit.: the problem comes from JAWT drawing surfaces