RFR: 8364741: [asan] runtime/ErrorHandling/PrintVMInfoAtExitTest.java fails because output differs slightly

[Matthias Baesken]

On Fri, 31 Oct 2025 18:46:32 GMT, Afshin Zafari <azafari at openjdk.org> wrote:

>> I'm just spitballing here based on my experience listening to @xmas92 talk about ASAN in ZGC. Could it be that ASAN is reserving memory at the lower end of the virtual address space, making it difficult to get zero-based Compressed Oops. In that case, we need som extra memory to "efficiently implement null checks.", which turns out to be 2M in this case, which looks like an extra large page.
>> https://github.com/openjdk/jdk/blob/8236800deb5b99a027b0944f6c512c0f31d030df/src/hotspot/share/memory/memoryReserver.cpp#L612-L614
>
> Thanks for sharing your info. It describes the 2M diff in reserved amount.

So I think changing/relaxing the check

`output_detail.shouldContain("Java Heap (reserved=65536KB, committed=65536KB)");`

in case of asan-enabled binaries would make sense, we do not need to disable the whole test when running with asan.

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/28055#discussion_r2485556995