Posted by hharrison on Jan 27, 2014; 5:35pm
URL: https://forum.jogamp.org/JOGL-commit-166e5da-causes-deadlock-errors-in-Java-3D-tp4031305p4031388.html

Looking through the history of this callback from the Java3d side...it really doesn't expect any AWT modification to happen in the nativewindow destruction path, which is likely why it gets surprised by JAWTWindow here...I think your solution of pushing the listener removal to the AWT-EDT on the jogl side is likely best....but if I've analyzed it wrong, I will look again and put a similar solution in place on the Java3d side.

Harvey