Posted by Douglas Lyon on Dec 27, 2017; 3:01pm
URL: https://forum.jogamp.org/Jogl-Jogamp-on-Java-9-tp4038012p4038445.html

I put a main method to test canvas3d, as I think this is the focus of all the attention;
   public static void main(String[] args) {
        GraphicsConfiguration gc= Canvas3D
                .defaultGraphicsConfiguration();
        System.out.println("GraphicsConfiguration:"+gc);
    }
Using jdk9, just to make sure there is no stray jars floating around, the jvm dies pretty quick. I turned VERBOSE=true to get a few more bits of information;

Can the pipeline be done in software? I am thinking it would be good to get something to work, even if slowly.

Thanks!
 - Doug

/Library/Java/JavaVirtualMachines/jdk-9.0.1.jdk/Contents/Home/bin/java -javaagent:/Applications/idea.app/Contents/lib/idea_rt.jar=53759:/Applications/idea.app/Contents/bin -Dfile.encoding=UTF-8 -classpath /Users/lyon/current/java/testHello/out/production/testHello:/Users/lyon/current/java/testHello/jars/jogamp-fat.jar javax.media.j3d.Canvas3D
3D @VERSION_BASE@-@VERSION_SUFFIX@-experimental @BUILDTIME_VERBOSE@

Initializing 3D runtime system:
    version = @VERSION_BASE@-@VERSION_SUFFIX@-experimental @BUILDTIME_VERBOSE@
    vendor = @IMPL_VENDOR@ & docjava.com
    specification.version = 1.6
    specification.vendor = @SPEC_VENDOR@

WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by javax.media.j3d.JoglPipeline (file:/Users/lyon/current/java/testHello/out/production/testHello/) to method sun.awt.AppContext.getAppContext()
WARNING: Please consider reporting this to the maintainers of javax.media.j3d.JoglPipeline
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
JoglPipeline.getMaximumLights()
3D system initialized
    rendering pipeline = JOGL

JoglPipeline.getBestConfiguration()
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x000000012e14d0cc, pid=33972, tid=775
#
# JRE version: Java(TM) SE Runtime Environment (9.0+11) (build 9.0.1+11)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (9.0.1+11, mixed mode, tiered, compressed oops, g1 gc, bsd-amd64)
# Problematic frame:
# C  [libosxapp.dylib+0x20cc]  -[NSApplicationAWT sendEvent:]+0x179
#
# No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /Users/lyon/current/java/testHello/hs_err_pid33972.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
#

Process finished with exit code 134 (interrupted by signal 6: SIGABRT)