Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8305957 | 8u381 | Daniel Skantz | P3 | Resolved | Fixed | b02 |
The test description is:
"Test that auxiliary data structures are allocated using large pages if available."
However, on systems with Huge Page support, this may fail because the huge pages may be extremely large (~1/2 - 1 GB) and the test tries to allocate memory way beyond physical memory in the system.
On systems with Huge Page support, the test tries to allocate pages with the large page size * 512. This can be over 250 GB, which is larger than many systems actually have.
From https://wiki.debian.org/Hugepages#Multiple_huge_page_size_support, it indicates that huge page sizes can be 512 MB for Arm64 systems and 1 GB for x86_64 systems.
This results in the test trying to allocate 256GB (Arm64) or 512 GB (x86_64), which is typically beyond what is actually available.
"Test that auxiliary data structures are allocated using large pages if available."
However, on systems with Huge Page support, this may fail because the huge pages may be extremely large (~1/2 - 1 GB) and the test tries to allocate memory way beyond physical memory in the system.
On systems with Huge Page support, the test tries to allocate pages with the large page size * 512. This can be over 250 GB, which is larger than many systems actually have.
From https://wiki.debian.org/Hugepages#Multiple_huge_page_size_support, it indicates that huge page sizes can be 512 MB for Arm64 systems and 1 GB for x86_64 systems.
This results in the test trying to allocate 256GB (Arm64) or 512 GB (x86_64), which is typically beyond what is actually available.
- backported by
-
JDK-8305957 JTReg failure: gc/g1/TestLargePageUseForAuxMemory.java
-
- Resolved
-