Posted by opqdonut on Jul 26, 2010; 10:48am
URL: https://forum.jogamp.org/Bug-in-GLContextLock-tp995870.html

Hi,

We bumped into a weird deadlock related to GLContext.makeCurrent(). It seems that one of our threads changes its name and this makes the following code snippet go wrong:

(GLContextLock:62)

Thread current = Thread.currentThread();
if (owner == null) {
    owner = current;
} else if (owner != current) {
      ...  // wait for lock
}

You see, the objects returned by currentThread() are not the same in our case, even though the thread is the same (the name changed). This causes a deadlock since the GLContextLock is waiting for itself :)

You should probably use Thread.equals() instead of ==. I also recommend considering some of the standard lock primitives instead of a custom one.