JDK-8251302 : Create dedicated OopStorages for Management and Jvmti
- Type: Bug
- Component: hotspot
- Sub-Component: svc
- Affected Version: 16
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2020-08-07
- Updated: 2024-11-20
- Resolved: 2020-08-11
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 b11Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
These facilities should have their own OopStorages so that GC can track scanning times for these components. Also Jvmti and Management uses of OopStorage are bursty, in that they are created and released after the operation is complete. Having dedicated oopstorages will more easily identify if OopHandles are leaked.
Comments
|