JDK-8249877 : Shenandoah: Report number of dead weak oops during STW weak roots
- Type: Bug
- Component: hotspot
- Sub-Component: gc
- Affected Version: 8-shenandoah,11.0.9,15,16
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2020-07-22
- Updated: 2020-08-05
- Resolved: 2020-07-22
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 :
|
Description
MemberNameLeak test is failing when running in STW mode, because ResolvedMethodTable never receives a gc_notification() call, which is usually done by calling report_num_dead() on the corresponding oop-storage. We do that in concurrent-weak-processing, but apparently not during STW weak processing.
Comments
|