JDK-6724890 : Deadlock between AWT-EventQueue-1 and AWT-XAWT threads during IDE start
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 6,7
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: generic,linux,windows
  • CPU: generic,x86
  • Submitted: 2008-07-11
  • Updated: 2011-05-11
  • Resolved: 2011-03-07
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 6 JDK 7
6u27Fixed 7 b55Fixed
Related Reports
Duplicate :  
Duplicate :  
Duplicate :  
Duplicate :  
Relates :  
Relates :  
Relates :  
Relates :  
Description
It happenned during NetBeans IDE start. Thread dump attached. JDK 7b30, Ubuntu Hardy 8.04, Linux 2.6.24-19-generic #1 SMP Wed Jun 18 14:43:41 UTC 2008 i686 GNU/Linux. Not reproducible.
It happens again with 1.7.0-ea-b36. I will attach new thread dump. Linux mslama-nb 2.6.24-21-generic #1 SMP Mon Aug 25 17:32:09 UTC 2008 i686 GNU/Linux

Comments
SUGGESTED FIX the fix is to use 'object' lock instead of 'this' lock to synchronize getExtendedState|setExtendedState methods. http://sa.sfbay.sun.com/projects/awt_data/7/6724890
12-02-2009

EVALUATION I guess this must not be reproducible after the fix for 6708322 is integrated.
11-07-2008