JDK-8247808 : Move JVMTI strong oops to OopStorage
- Type: Enhancement
- Component: hotspot
- Sub-Component: jvmti
- Affected Version: 16
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2020-06-17
- Updated: 2024-11-13
- Resolved: 2020-07-16
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 b07Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
There are a few oops in JVMTI that are walked by all the GCs through oops_do() functions. They should be relocated to OopStorageSet::vm_global() oops.
Comments
|