JDK-6908267 : Zero fails to unlock synchronized native methods on exception
- Type: Bug
- Component: hotspot
- Sub-Component: runtime
- Affected Version: hs17
- Priority: P4
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2009-12-08
- Updated: 2012-10-08
- Resolved: 2010-01-19
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 6 | JDK 7 | Other |
|---|---|---|
6u21Fixed  |
7Fixed |
hs17Fixed |
Related Reports
|
Relates :
|
Description
If a synchronized native method throws an exception, Zero does not unlock it. This leaves the object locked, with a stale monitor, which can cause the VM will crash at some unspecified time in the future.
Comments
|