JDK-8138764 : In some cases the usage of TreeLock can be replaced by other synchronization
- Type: Bug
- Component: client-libs
- Sub-Component: java.awt
- Affected Version: 8,9
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2015-10-02
- Updated: 2016-04-27
- Resolved: 2015-10-21
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.
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 | JDK 9 |
|---|---|
8u101Fixed  |
9 b92Fixed |
Related Reports
|
Relates :
|
Description
AWTTreeLock is a static lock, which should be used for the cases when we iterates over hierarchy of components, or in the code, which cannot use OtherLock, because it cannot control the order of OtherLock vs AWTTreeLock. AWTTreeLock should be used carefully, because if it is used incorrectly it can cause a deadlock. especially if used by the multiple threads via awt library. https://www.google.com/search?q=AWTTreeLock+deadlock