RFR: 8265349: vmTestbase/../stress/compiler/deoptimize/Test.java fails with OOME due to CodeCache exhaustion.
iignatyev at openjdk.java.net
Wed Apr 28 16:04:52 UTC 2021
On Wed, 28 Apr 2021 14:02:16 GMT, Evgeny Nikitin <enikitin at openjdk.org> wrote:
> The bug: https://bugs.openjdk.java.net/browse/JDK-8265349
> A repetition of the JDK-8058176 (mlvm tests cause code cache exhaustion), this time with -Xcomp. My measurements show up max code cache consumption of 400-500 kb per test thread and tree (depends on random tree and other factors, of course, but still). For the whole test which usually doesn't exceed 10 threads, I've got max. value of 6.1M for one sequence/tree build (between checks for remaining free space).
> So I suggest to raise the allowances to 10M, just to be safe. Compared to the 103 Mb of required code cache space that test requests via the 'run' parameter, it doesn't look that much.
> Thanks in advance,
> // Evgeny Nikitin.
Will it make sense to make `NON_SEGMENTED_CACHE_ALLOWANCE` / `SEGMENTED_CACHE_ALLOWANCE` value dependent on `Platform::isComp`?
More information about the hotspot-compiler-dev