Bug ID: JDK-8196611 [Graal] Tests unaware of objects allocation triggered by Graal

Type: Bug
Component: hotspot
Sub-Component: compiler
Affected Version: 11

Priority: P3
Status: Open
Resolution: Unresolved

Submitted: 2018-02-01
Updated: 2020-08-07

Other
tbdUnresolved

There is set of tests which expect that no objects allocation is done in case it is not triggered by application code.
This is not anymore true in case Graal is used as JIT compiler. 

At least following tests fail because of this:
 java/lang/Runtime/exec/LotsOfOutput.java
 java/lang/ref/OOMEInReferenceHandler.java

-Xcomp mode:
 gc/arguments/TestNewSizeFlags.java
 gc/g1/TestConcurrentSystemGC.java

Until JDK-8238728 is fixed this issue (Java heap is used by Graal) affects libgraal too.
11-02-2020
One more OutOfMemory failure "com/sun/crypto/provider/KeyFactory/TestProviderLeak.java" Created SubTask JDK-8230454 to add it into Graal problem list
03-09-2019
Please also consider issues added as duplicates.
24-04-2019
More OtuOfMemory failures: vmTestbase/gc/gctests/LargeObjects/large001/large001.java vmTestbase/gc/gctests/ReferencesGC/ReferencesGC.java
15-04-2019
Following jdi tests launch debugee with -Xmx256M and as result debugee process could fail with "java.lang.OutOfMemoryError: Java heap space" vmTestbase/nsk/jdi/VirtualMachine/instanceCounts/instancecounts003/instancecounts003.java vmTestbase/nsk/jdi/ObjectReference/referringObjects/referringObjects002/referringObjects002.java "grep -R "\-debugee.vmkeys=\-Xmx" vmTestbase/nsk/jdi/" will list more tests which could fail similar way.
15-04-2019
The test from JDK-8200186 gc/parallel/TestPrintGCDetailsVerbose.java
18-01-2019
I think we should exclude from running with Graal such tests and tests which fills up Java heap and watching OOME.
10-07-2018
2 more failures observed on windows. - vmTestbase/nsk/stress/except/except007.java ... Uncaught exception while adjusting compilation level: java.lang.OutOfMemoryError: Java heap space java.lang.OutOfMemoryError: Java heap space <<no stack trace available>> Uncaught exception while adjusting compilation level: java.lang.OutOfMemoryError: Java heap space java.lang.OutOfMemoryError: Java heap space <<no stack trace available>> Uncaught exception while adjusting compilation level: java.lang.OutOfMemoryError: Java heap space java.lang.OutOfMemoryError: Java heap space <<no stack trace available>> Uncaught exception while adjusting compilation level: java.lang.OutOfMemoryError: Java heap space java.lang.OutOfMemoryError: Java heap space <<no stack trace available>> Skipped: InterruptedException Skipped: NegativeArraySizeException Skipped: NullPointerException Skipped: NumberFormatException Timeout refired 1200 times - vmTestbase/nsk/stress/except/except008.java ... Skipped: NoSuchFieldException positive check - OutOfMemoryError thrown NoSuchFieldException negative check - OutOfMemoryError thrown Skipped: NoSuchMethodException positive check - OutOfMemoryError thrown Skipped: NoSuchMethodException negative check - OutOfMemoryError thrown Timeout refired 1200 times ----------System.err:(2/90)---------- java.lang.OutOfMemoryError: Java heap space java.lang.OutOfMemoryError: Java heap space
10-07-2018
gc/g1/mixedgc/TestOldGenCollectionUsage.java failed with ---------System.err:(14/940)---------- java.lang.RuntimeException: Premature mixed collections(s) at TestOldGenCollectionUsage.run(TestOldGenCollectionUsage.java:106) at TestOldGenCollectionUsage.main(TestOldGenCollectionUsage.java:58) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at com.sun.javatest.regtest.agent.MainWrapper$MainThread.run(MainWrapper.java:115) at java.base/java.lang.Thread.run(Thread.java:834) because the test seems to be based on the assumption that the compiler performs no allocation not true for Graal).
10-07-2018
java/util/concurrent/ScheduledThreadPoolExecutor/BasicCancelTest.java is launched with -Xmx8m and intermittently fails with OOM
14-05-2018
This problem should go away once we run Graal in SVM mode. Should we add @require statements to these tests for as long as we don't have a Graal specific problem list? We should also make sure that we then add other currently ignored tests to this list (and remove the @require tag). This allows us to easily re-enable all these tests once SVM is available. ILW = Tests fail due to allocations triggered by Graal (test bug), several tests with Graal as JIT, use C2 = MMM = P3
02-02-2018

Duplicate :	JDK-8222820 - gc/g1/ihop/TestIHOPStatic.java failed with exit code 255
Duplicate :	JDK-8200186 - [Graal] gc/parallel/TestPrintGCDetailsVerbose.java fails with OOM
Duplicate :	JDK-8223739 - serviceability/dcmd/gc/HeapDumpAllTest.java timeout with Graal
Relates :	JDK-8207267 - Enable tests which currently do not run with Java Graal to run with libgraal
Relates :	JDK-8186299 - [Graal] vm/mlvm/anonloader/stress/oome/heap fails with OOM in Metaspace
Relates :	JDK-8218176 - [graal] gc tests fail with OutOfMemoryError
Relates :	JDK-8218166 - com/sun/jdi/SimulResumerTest.java failure
Relates :	JDK-8204853 - [JVMCI][Graal] add support for AOT compiling Graal with SubstrateVM
Relates :	JDK-8210193 - [TESTBUG]gc/g1/mixedgc/TestOldGenCollectionUsage.java fails intermittently with OutOfMemoryError in CDS mode
Relates :	JDK-8236139 - [Graal] java/lang/RuntimeTests/exec/LotsOfOutput.java fails with JVMCI enabled