openjdk team mailing list archive
-
openjdk team
-
Mailing list archive
-
Message #11398
[Bug 1510009] Re: Java 1.8.0_66 is extremely deadlock prone regarding AWT/GTK interaction
src/solaris/native/sun/awt/awt_UNIXToolkit.c:
AWT_LOCK();
XSync(awt_display, False);
AWT_UNLOCK();
Looks like X11 is supposed to be protected by AWT_LOCK.
src/solaris/classes/sun/awt/UNIXToolkit.java:
/** All calls into GTK should be synchronized on this lock */
public static final Object GTK_LOCK = new Object();
It looks like also gtk is protected with a java lock.
Mean while looking at java-atk-wrapper code it is using gtk/atk/gdk
without unix toolkit lock.
But I simple can't remember any specific reason to use locks if opening
two separate X display for two threads.
Also I can't understand how gdk_open_display can hit a race condition
...
--
You received this bug notification because you are a member of OpenJDK,
which is subscribed to openjdk-8 in Ubuntu.
https://bugs.launchpad.net/bugs/1510009
Title:
Java 1.8.0_66 is extremely deadlock prone regarding AWT/GTK
interaction
Status in openjdk-8 package in Ubuntu:
Confirmed
Bug description:
Since upgrading to Ubuntu 15.10 from Ubuntu 15.04, the various GUI
applications that I run, including Netbeans and Minecraft have been
suffering from dead/waitlocks which prevent them from operating
properly. Since I have reproduced this issue these two completely
different codebases, I am moving the bug further upstream.
The original Netbeans bug report can be viewed here: https://netbeans.org/bugzilla/show_bug.cgi?id=256124
Essentially, during routine interaction and calling of various AWT methods, somewhere between 8u45 (15.04) and 8u66 (15.10), something broke causing the application to hang intermittently when these methods are called.
Some sample jstack traces are attached, the issue should be fairly
obvious to spot.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjdk-8/+bug/1510009/+subscriptions
References