Posted by xghost on Aug 22, 2014; 8:50am
URL: https://forum.jogamp.org/Need-Help-Solving-OpenGL-GLSL-4-4-Issues-tp4032557p4032887.html

Sven Gothel wrote

I assume you use version 2.2.0?

I tried it in the previous (i.e March 2014) release and also now in 2.2.0 (August 2014 release). It's the same behavior for both.

Sven Gothel wrote

Looks similar to an AMD Windows driver Bug 1028
<https://jogamp.org/bugzilla/show_bug.cgi?id=1028>.

I'm using a 64-bit GNU/Linux system and an NVIDIA card (GTX 770). I had taken a look at that bug before, but it seems unrelated.

Sven Gothel wrote

At launch, we kick-off a SharedResourceRunner thread holding an
OpenGL context to probe capabilities.
If this is not properly shutdown, the AMD Windows driver keeps
the application from terminating. A driver bug.

See previous data about OS/environment.

Sven Gothel wrote

System.exit(0) should cause our shutdown hook to be called, hmm.
Try GLProfile.shutdown() and then System.exit(0) - if you must.

I tried adding the GLProfile.shutdown() call first, but it made no difference. I still get the same result.

Sven Gothel wrote

Which OpenGL driver do you use ?

Currently using NVIDIA driver 331.38 for 64-bit GNU/Linux.

Sven Gothel wrote

Maybe you can add a 'jstack -l PID >& jstack.log'
output to your new bug report.

Thank you.

~Sven

Will do.