JDK-8129119 : Consider reducing the time while the AWTLock is held
  • Type: Enhancement
  • Component: client-libs
  • Priority: P4
  • Status: Open
  • Resolution: Unresolved
  • Submitted: 2015-06-18
  • 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 :  
Description
There are several deadlock fixes JDK-8129116, JDK-7155963, JDK-7158311. All of them are about to release the awtLock in each particular case to avoid deadlocking. This pattern doesn't look good to me. 
Currently we are dispatching events in XToolkit under the awtLock. We should consider to release the lock upon dispatchEvent() call in XToolkit and acquire it only when necessary.