RFR: 8265349: vmTestbase/../stress/compiler/deoptimize/Test.java fails with OOME due to CodeCache exhaustion.

[Evgeny Nikitin]

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.

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

Commit messages:
 - 8265349: vmTestbase/../stress/compiler/deoptimize/Test.java fails with OOME due to CodeCache exhaustion

Changes: https://git.openjdk.java.net/jdk/pull/3762/files
 Webrev: https://webrevs.openjdk.java.net/?repo=jdk&pr=3762&range=00
  Issue: https://bugs.openjdk.java.net/browse/JDK-8265349
  Stats: 5 lines in 2 files changed: 0 ins; 2 del; 3 mod
  Patch: https://git.openjdk.java.net/jdk/pull/3762.diff
  Fetch: git fetch https://git.openjdk.java.net/jdk pull/3762/head:pull/3762

PR: https://git.openjdk.java.net/jdk/pull/3762