Ironically, that test now fails on AIX, where we use SystemV shared memory which has the same semantics as the Windows virtual memory API. See also
(Note that we may have a similar problem on Linux where we use System V shm for large pages with +UseSHM - but there, this type of memory is restricted to os::reserve_memory_special, and therefore the os.release_one_mapping_multi_commits_vm gtest does not fail, since it only tests the interplay of os::release_memory() with the standard os::reserve_memory()).
- relates to
-
JDK-8255978 [windows] os::release_memory may not release the full range
-
- Resolved
-
-
JDK-8257040 [posix] os::split_reserved_memory will not work as expected on SysV shm
-
- Closed
-
-
JDK-8257042 [aix] Disable os.release_one_mapping_multi_commits_vm gtest
-
- Resolved
-