Please perform a runtime version check, which provides the following information:

• Platform
• OS & version
• Architecture
• OpenGL Version
• Java version (java -version)
• JOGL version
• GIT revision
• Autobuild version

SEND us the resulting file

test.log
.
Detailed Debug Log
Please perform a runtime debug test.
Send us the resulting file
test_dbg.log
.

Detailed Bug Information

• Your Test case
• Source code, a junit test would be best.
• Invocation command-line
• Exceptions, stdout/stderr log file

Applications

Adding a comprehensive junit test would help us the most to reproduce the bug, to discuss it with you and to achieve a good response time.

You may add it to your bug report directly or better, give us your git repository pull request.

If possible, please add the following system properties to enable DEBUG logging: -Dnewt.debug=all -Dnativewindow.debug=all -Djogl.debug=all

For example:

java -Djava.awt.headless=true -Dnewt.debug=all -Dnativewindow.debug=all

-Djogl.debug=all demos.es2.RedSquare 2>&1 | tee RedSquare.report.log

Attach the log file to your bug report ..

Applets and Java Webstart

To test applets and javaws use

• the jcontrol panel
• or edit the java properties file:
• Unix: ~/.java/deployment.properties
• Windows: Users<username>AppDataLocalLowSunJavaDeploymentdeployment.properties

where you add the following JRE ARGUMENTS. The jnlp prefix supports the javaws launch method.

• jcontrol panel:
  -Djnlp.newt.debug=all -Djnlp.nativewindow.debug=all -Djnlp.jogl.debug=all
• properties file:
  deployment.javaws.jre.0.args=-Djnlp.newt.debug=all -Djnlp.nativewindow.debug=all -Djnlp.jogl.debug=all

Of course you have to add these arguments to all of your JRE lines, ie 0 and 1, etc, if they exist.

You also want to

• Enable logging/trace
• Show the CONSOLE window, or just use the latest log files in
• Unix: ~/.java/deployment/log/, or
• Windows: Users<username>AppDataLocalLowSunJavaDeploymentlog

Hence the java properties file (see location above) shall contain the following:

...
deployment.log=true
deployment.trace=true
deployment.javaws.jre.0.args=-Djnlp.newt.debug=all -Djnlp.nativewindow.debug=all -Djnlp.jogl.debug=all
deployment.javaws.jre.1.args=-Djnlp.newt.debug=all -Djnlp.nativewindow.debug=all -Djnlp.jogl.debug=all
...

Best practice:

• Close your browser and ensure no JVM is running anymore
• Delete all old log files in above log file folder
• Start browser and the test applet
• Close browser after test .. maybe after a while if you see nothing
• Attach all new generated *.trace files to your bug report ..

Please perform a runtime version check, which provides the following information:

Send us the resulting file

test.log
.
Detailed Debug Log
Please perform a runtime debug test.
Send us the resulting file
test_dbg.log
.

Detailed Bug Information

Applications

Adding a comprehensive junit test would help us the most to reproduce the bug, to discuss it with you and to achieve a good response time.

You may add it to your bug report directly or better, give us your git repository pull request.

If possible, please add the following system properties to enable DEBUG logging: -Dnewt.debug=all -Dnativewindow.debug=all -Djogl.debug=all

For example:

java -Djava.awt.headless=true -Dnewt.debug=all -Dnativewindow.debug=all

-Djogl.debug=all demos.es2.RedSquare 2>&1 | tee RedSquare.report.log

Attach the log file to your bug report ..

Applets and Java Webstart

To test applets and javaws use

where you add the following JRE Arguments. The jnlp prefix supports the javaws launch method.

Of course you have to add these arguments to all of your JRE lines, ie 0 and 1, etc, if they exist.

You also want to

Hence the java properties file (see location above) shall contain the following:

...
deployment.log=true
deployment.trace=true
deployment.javaws.jre.0.args=-Djnlp.newt.debug=all -Djnlp.nativewindow.debug=all -Djnlp.jogl.debug=all
deployment.javaws.jre.1.args=-Djnlp.newt.debug=all -Djnlp.nativewindow.debug=all -Djnlp.jogl.debug=all
...

Best practice: