Posted by gouessej on Dec 30, 2017; 6:02pm
URL: https://forum.jogamp.org/Jogl-Jogamp-on-Java-9-tp4038012p4038457.html

Please rather make a pull request instead of "sharing" a 7z archive. Moreover, I'm sorry but the real fix would consist in avoiding a crash when releasing the context. You cannot spot any memory leak because you don't look at the right place. The allocated memory is in the native heap, not in the Java heap.

We are open to contributions but please don't add any confusion by offering an alternative version of Java3D without allowing us to see exactly what you changed. That's why I insist on the pull request. Please make an effort to follow our guidelines so that we can work together.

Do you reproduce the same crash when leaving a program based on JOGL but not on Java3D?
https://gist.github.com/gouessej/3420e2b6f632efdddf98

If the program above works correctly with Java 1.9 under OS X, it means that the culprit is really in Java3D, otherwise we have something to fix in JOGL.