Posted by gouessej on Jan 07, 2011; 10:33am
URL: https://forum.jogamp.org/high-memory-consumption-in-JOGL-tp2141331p2210985.html

Some people negociated to backport the fix done in Java 1.7 in Java 1.6. In my humble opinion, this workaround is still needed as some people still uses IcedTea and some other JVM that does not contain this "recent" fix.

The other fixes are almost mandatory when you mix AWT, Swing and SWT especially when you want to use the debug pipeline.

Have you noticed that when you use several SWT Composite instances with the embedded style, on some platforms, it does not work, the last Composite instance is not displayed?