JDK-8261230 : GC tracing of page sizes are wrong in a few places
- Type: Bug
- Component: hotspot
- Sub-Component: gc
- Affected Version: 17
- Priority: P4
- Status: Resolved
- Resolution: Fixed
- Submitted: 2021-02-05
- Updated: 2021-02-23
- Resolved: 2021-02-12
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 17 |
|---|
17 b10Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
|
|
Relates :
|
Description
G1, Paralle and Serial all log incorrect page sizes with os::trace_pages(). For G1 the parameter order is wrong and in Parallel and Serial the large_page_size will always be used even if the mappings fail. I've created a test that catch those issues but there are also problems when tracing the code heaps (see JDK-8261029), so the test can't be added until a fix for that is integrated as well. The test is available here for now: https://github.com/kstefanj/jdk/tree/test-for-trace-page-sizes
Comments
|