Re: high memory consumption in JOGL
Posted by
Sven Gothel on
Jan 02, 2011; 1:39am
URL: https://forum.jogamp.org/high-memory-consumption-in-JOGL-tp2141331p2178217.html
On Saturday, January 01, 2011 16:29:32 gouessej [via jogamp] wrote:
>
> 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.
sure, I will check AWT/GLCanvas with jvisualvm
and try to remove any of those temp objects.
hopefully one of the simple gears unit tests will make
such odd behavior visible.
as you might know, we already fought temp objects lately,
so such a regression as you described is for sure not welcome :)
~Sven