Posted by The.Scotsman on
URL: https://forum.jogamp.org/Incomplete-shutdown-Eclipse-tp4025154p4025163.html

Wade Walker wrote

I've noticed this before on Linux (though not lately). If you run your app in debug mode, then hit the "pause" button in Eclipse instead of shutting Eclipse down, it should break all threads so you can see who's still running and where they are in the code (you might need to attach source to JOGL to see the details).

I tried that before posting. Just says 'javaw.exe'.

Commented out stuff and isolated it to a single call:
  canvas = new GLCanvas();

Removing this and shutdown is clean.
Added 'canvas.destroy()' to the shutdown method (inside a SwingUtilities.invokeAndWait), but it didn't help...

If jogamp is not the problem, I guess that leaves Eclipse (using 3.5) and the graphics driver (Catalyst 12.4/OpenGL 6.14.10.11631).
Will have to try on another PC.

Thanks for all the input.