JDK-8029069 : [TESTBUG] test/compiler/8002069/Test8002069.java might throw OutOfMemoryError when additional Java code is running
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Priority: P5
  • Status: Closed
  • Resolution: Won't Fix
  • OS: generic
  • CPU: generic
  • Submitted: 2013-11-23
  • Updated: 2016-12-19
  • Resolved: 2014-07-01
Related Reports
Relates :  
JDK-8002069 - Assert failed in C2: assert(field->edge_count() > 0) failed: sanity
Description
With a Java heap size of 32MB memory pressure when running with Graal might become too big and an OutOfMemoryError gets thrown:

cthaling@macbook:~/ws/graal/test/compiler/8002069$ $PRODUCT_HOME/bin/java -Xmx32m -XX:+IgnoreUnrecognizedVMOptions -Xbatch -XX:CompileCommand=exclude,Test8002069.dummy Test8002069
CompilerOracle: exclude Test8002069.dummy
Bootstrapping Graal.........................java.lang.OutOfMemoryError: GC overhead limit exceeded
Comments
We need to handle this situation differently.
01-07-2014
There are other tests that have the same problem, e.g.: compiler/7199742/Test7199742.java
26-11-2013
Maybe we should do the same as JDK's test/Makefile does: # Set the max memory for jtreg target test vms JTREG_TESTVM_MEMORY_OPTION = -vmoption:-Xmx512m JTREG_TEST_OPTIONS += $(JTREG_TESTVM_MEMORY_OPTION)
23-11-2013
In JDK-8002069 Vladimir wrote: "Because the test uses less then 10Mb. In 64-bit VM on big machines it takes time to initialize 1/4 of physical memory. So it is not related to test functionality but how long test runs. You can increase size if you need."
23-11-2013