Deadlocks in JOGL/AWT

OpenGL Development JOGL Development
#1

I have a question for the great JOGL/AWT gurus.

We have an app that has a JOGL piece as well as a significant amount of Swing/AWT around it. We noticed that when the JOGL display thread blocks, (not really our intention, but it’s been happening lately) we’ve noticed that all of our AWT stuff blocks as well. I assume that there is some native semaphore/other locking mechanism in place that is causing this. (This is on Linux) This would certainly explain why JOGL and AWT don’t play well together.

My question is this: Is this locking happening at a native level in the JVM, or is this happening at an OS/X11 level. I would appreciate any insight anyone can give into this.

#2

The locking is occurring inside the AWT Native Interface (JAWT) on X11, which is used by JOGL to get a handle to the underlying widget for a Canvas to be able to attach an OpenGL context. There is an RFE filed about this behavior: 4852178.

#3

Many thanks for answering my question.