RFR: 8371320: runtime/ErrorHandling/PrintVMInfoAtExitTest.java fails with unexpected amount for Java Heap reserved memory

Afshin Zafari azafari at openjdk.org
Fri Nov 7 11:14:13 UTC 2025


On Thu, 6 Nov 2025 16:36:33 GMT, Paul Hübner <phubner at openjdk.org> wrote:

> Hi all,
> 
> In [JDK-8364741](https://bugs.openjdk.org/browse/JDK-8364741) it was discovered that asan reserves a bit more heap. The test got patched by checking for asan and adjusting the expectation, respectively.
> 
> It turns out that, rarely, we do reserve more memory even without asan enabled. This change updates the test:
> a) to ensure that some sort of reservation size is reported; and
> b) to extract the reserved amount and assert that it is no less than the committed amount
> 
> Testing: Ran tier1. Stress tested the individual test with 5x100 repetitions per platform (Linux x64, AArch64; macOS x64, AArch64; Windows x64).

Thank you @Arraying for taking this.
The condition of `reserved < committed` is/should be always true, otherwise NMT is not doing its tasks correctly.
I suggest to check if the reported amount of `reserved` (and `committed` for a restricter condition) is at least 64M (which is given as options in command line).

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

PR Review: https://git.openjdk.org/jdk/pull/28179#pullrequestreview-3433132003


More information about the hotspot-runtime-dev mailing list