JDK-8067252 : Investigate the possibility of splitting dispatchEvent in XToolkit to dispatch event w/ and w/o awtLock.
  • Type: Enhancement
  • Component: client-libs
  • Sub-Component: java.awt
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2014-12-11
  • Updated: 2018-09-05
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.
Other
tbdUnresolved
Related Reports
Relates :  
JDK-8001463 - Regression : Deadlock between AWT-XAWT thread and AWT-EventQueue-0 Thread when screen resolution changes
Relates :  
JDK-7155963 - Deadlock in SystemFlavorMap.getFlavorsForNative and SunToolkit.awtLock
Description
Currently we always dispatching events under awtLock in XToolkit. However, there are some issues, where this lock is unnecessary or even harmful (like JDK-7155963 JDK-8001463). Probably this can be improved by splitting dispatchEvent in XToolkit to dispatch events w/ and w/o awtLock.