JDK-8077255 : TracePageSizes output reports wrong page size on Windows with G1
- Type: Bug
- Component: hotspot
- Sub-Component: gc
- Affected Version: 9
- Priority: P5
- Status: Resolved
- Resolution: Fixed
- Submitted: 2015-04-08
- Updated: 2015-09-29
- Resolved: 2015-04-10
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 8 | JDK 9 |
|---|---|
8u60Fixed  |
9 b64Fixed |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
Sometimes the test in gc/g1/TestLargePageUseForAuxMemory fails because the output with -XX:+TracePageSizes reports a page size of 64k (= allocation granularity). This makes that test fail, failing jprt. Cause for this problem has been some wrong refactoring.
Comments
|