JDK-6951784 : Zero deoptimizer changes
- Type: Bug
- Component: hotspot
- Sub-Component: runtime
- Affected Version: hs18
- Priority: P4
- Status: Closed
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2010-05-12
- Updated: 2012-10-08
- Resolved: 2010-05-18
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 |
|---|---|---|
| 6u21pFixed | 7Fixed  |
hs19Fixed |
Description
Gary Benson wrote: Hi all, The way Zero currently handles deoptimization can lead to methods being freed while they are still being executed, with the obvious consequences. This webrev fixes: http://cr.openjdk.java.net/~gbenson/zero-deopt-fix/ I don't have a bug id for this. Cheers, Gary
Comments
|