JDK-8015471 : Deadlock or infinit loop in XAWT on Ubuntu 12.04
  • Type: Bug
  • Component: client-libs
  • Sub-Component: 2d
  • Affected Version: 8
  • Priority: P2
  • Status: Closed
  • Resolution: Cannot Reproduce
  • OS: linux
  • CPU: generic
  • Submitted: 2013-05-28
  • Updated: 2015-07-31
  • Resolved: 2013-10-14
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
JDK 8
8Resolved
Related Reports
Duplicate :  
JDK-8129116 - Deadlock with multimonitor fullscreen windows.
Relates :  
JDK-8015730 - PIT: On Linux, OGL=true and fbobject=false leads to deadlock or infinite loop
Description
Testsuite name: 2D

JDK/JRE tested: 1.8.0_b91
OS/architecture: Ubuntu 12.04 x64
Reproducible: From times to times
Reproducible on machine: aeremeev-ru
Is it a Regression: No
Is it a platform specific issue: Yes

Deadlock hangs JVM.
Stack dump attached.

To reproduce use attached files.
Compile and run it with flag "-perf"
Comments
I ran on my current build (approx JDK 8 b112) > 20 times without problem I noted the comment about 8015730. That was fixed in jdk8 b100 so I ran JDK8 b99 20 times and also no deadlock although one run with that build did get an exception that didn't stop the test :- 700 x 700 volatile 35 Exception in thread "AWT-EventQueue-0" java.lang.NullPointerException at sun.awt.image.SunVolatileImage.getBackupImage(SunVolatileImage.java:236) at sun.awt.image.VolatileSurfaceManager.getBackupSurface(VolatileSurfaceManager.java:263) at sun.awt.image.VolatileSurfaceManager.initialize(VolatileSurfaceManager.java:126) at sun.awt.image.SunVolatileImage.<init>(SunVolatileImage.java:88) at sun.awt.image.SunVolatileImage.<init>(SunVolatileImage.java:98) at sun.awt.image.SunVolatileImage.<init>(SunVolatileImage.java:109) at sun.awt.image.SunVolatileImage.<init>(SunVolatileImage.java:103) at sun.awt.X11.XComponentPeer.createVolatileImage(XComponentPeer.java:744) at java.awt.Component.createVolatileImage(Component.java:3597) at VolatileDuke.initOffscreen(VolatileDuke.java:158) at VolatileDuke.paint(VolatileDuke.java:289) at javax.swing.RepaintManager$3.run(RepaintManager.java:822) at javax.swing.RepaintManager$3.run(RepaintManager.java:794) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$1.doIntersectionPrivilege(ProtectionD ----- Since I can't reproduce this (on my Ubuntu 13.04 box) I am closing this out.
14-10-2013
This bug reproduced again. Maybe it relates to JDK-8015730
08-07-2013
Today I run this test more than 20 times and I have no deadlock. Maybe, it is a bug in Ubuntu.
30-05-2013
I am also not sure I can trust (or may be its just properly understand) the VM output. It says Found one Java-level deadlock: ============================= "AWT-EventQueue-0": waiting for ownable synchronizer 0x00000000d7d43118, (a java.util.concurrent.locks.ReentrantLock$NonfairSync), which is held by "AWT-XAWT" "AWT-XAWT": waiting to lock monitor 0x00007f0e4c005ad8 (object 0x00000000d7d6e8c0, a java.lang.Object), which is held by "AWT-EventQueue-0" ------ But AWT-XAWT looks like this and I don't see where it holds any lock. Its just waiting on one .. "AWT-XAWT" #10 daemon prio=6 os_prio=0 tid=0x00007f0ea41ab000 nid=0xc16 waiting for monitor entry [0x00007f0e8b35b000] java.lang.Thread.State: BLOCKED (on object monitor) at sun.awt.X11GraphicsDevice.getDefaultConfiguration(X11GraphicsDevice.java:225) - waiting to lock <0x00000000d7d6e8c0> (a java.lang.Object) at sun.awt.X11.XWindowPeer.checkIfOnNewScreen(XWindowPeer.java:684) at sun.awt.X11.XDecoratedPeer.handleConfigureNotifyEvent(XDecoratedPeer.java:785) at sun.awt.X11.XBaseWindow.dispatchEvent(XBaseWindow.java:1135) at sun.awt.X11.XBaseWindow.dispatchToWindow(XBaseWindow.java:1090) at sun.awt.X11.XToolkit.dispatchEvent(XToolkit.java:581) at sun.awt.X11.XToolkit.run(XToolkit.java:690) at sun.awt.X11.XToolkit.run(XToolkit.java:611) at java.lang.Thread.run(Thread.java:724)
29-05-2013
Can you tell me if this reproduces on JDk8 b04 ?
29-05-2013
RULE 2D_VolatileDuke/VolatileDukePerf Timeout none
28-05-2013