Posted by Julien on Jan 24, 2014; 12:23am
URL: https://forum.jogamp.org/JOGL-commit-166e5da-causes-deadlock-errors-in-Java-3D-tp4031305p4031310.html

Julien & Harvey,

Thanks for the quick response. The call to

component.setVisible(localVisibility);

is not the problem. The problem is isolated to this change (in two places)

-            component.addComponentListener(jawtComponentListener);
-            component.addHierarchyListener(jawtComponentListener);
+            component.addComponentListener(this);
+            component.addHierarchyListener(this);

There is a fair bit of locking in JAWTWindow.java which I wonder if that is the source of the problem. Where ever the "this" object is escaping to may be causing deadlock. I tried playing around with removing the locks, but that experiment went nowhere.

For your request to provide a test case, how do I do that? This deadlock bug is the result of complex interactions between IDV, VisAD, Java 3D and JOGL. If you want, I can explain how to run the IDV to reproduce this problem.

Here is the full thread dump: https://gist.github.com/julienchastang/8589559

Thanks again for your help.

-Julien