JDK-5011050 : Perhaps Frame.getExtendedState() shouldn't be synchronized
- Type: Bug
- Component: client-libs
- Sub-Component: java.awt
- Affected Version: 6
- Priority: P4
- Status: Closed
- Resolution: Duplicate
- OS: generic
- CPU: generic
- Submitted: 2004-03-10
- Updated: 2009-12-28
- Resolved: 2009-12-28
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 7 |
|---|
7Resolved  |
Related Reports
|
Duplicate :
|
Description
Name: rpR10076 Date: 03/10/2004 In the past, we have encountered several deadlock conditions which involved Frame.getExtendedState(). We need to investigate whether we can rewrite this and several other methods on Frame so that it no longer needs to be synchronized. Historically, Frame.getState() was synchronized and then getExtendedState inherited it. ###@###.### ======================================================================
Comments
|