JDK-8237363 : Remove automatic is in heap verification in OopIterateClosure
- Type: Enhancement
- Component: hotspot
- Sub-Component: gc
- Affected Version: 15
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2020-01-16
- Updated: 2020-10-29
- Resolved: 2020-10-26
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 16 |
|---|
16 b22Fixed  |
Related Reports
|
Relates :
|
Description
OopIterateClosure provides some automatic verification that read objects are inside the heap. Closures can opt out from this by overriding should_verify_oops(). I propose that we remove this verification and let the closures do their own verification.
Comments
|