Posted by MarcoNL on Sep 07, 2022; 5:16pm
URL: https://forum.jogamp.org/Incorrect-context-on-GLCanvas-drawable-tp4041391p4041843.html

Hi Martin,

and thanks for the reply.

OK, so it looks like my report within this thread corresponds with issue #24 on this web page:

https://github.com/jzy3d/jogl/issues

Any chance of seeing this fixed in the near future in JOGL?

The suggested workaround of setting "-Dsun.awt.nopixfmt=true" works 99% of the times for me, but sometimes causes JOGL to crash anyway, with some specific graphics cards / display drivers.

For instance, today I dealt with a Win 10 PC having an NVIDIA Quadro K600 graphics adapter and running the latest compatible NVIDIA display driver, and my JOGL-based canvas (VTK's vtkJoglCanvasComponent, based on GLCanvas) caused a JVM crash as soon as the canvas was displayed in my application.

This PC actually had 2 graphics adapters connected to 3 monitors:

* Basic embedded graphics adapter connected to standard PC monitor (Screen 1)
* NVIDIA Quadro K600 connected to 2 medical displays (Screen 2 and Screen 3, EIZO 3 megapixels displays)

My application was running on the medical displays, and the container panels in turn containing VTK's vtkJoglCanvasComponent were indeed using a GraphicsConfiguration related to the NVIDIA Quadro K600 adapter.

On the other side, a very similar PC with the same monitor configuration, but using an NVIDIA Quadro K2000 adapter, was running fine with no crashes with my Java + VTK + JOGL application (always specifying "-Dsun.awt.nopixfmt=true").

Maybe, if this issue is fixed "at the root" in JOGL, I could avoid adopting the "-Dsun.awt.nopixfmt=true" workaround, and my application wouldn't crash also on such hardware configurations.

In case a financial contribution could help somehow in fixing this issue faster, I will be glad to consider it.

Thanks and regards,

Marco Sambin