Posted by Manu on Jan 16, 2013; 9:51am
URL: https://forum.jogamp.org/Simple-Java-3D-test-crashes-under-Windows-tp4027770p4027859.html

There must have been a change in Java 3D 1.6 that provokes this crash, since it works with Java 3D 1.3 to 1.5.2.
Is the call to javax.media.j3d.Canvas3D#updateSeparateSpecularColorEnable absolutely necessary?
If you don't get any valuable information from this call, isn't it possible to set some default value about the tested value?
In all cases, a program using native DLLs should never crash, so isn't it possible to catch some exception?