JDK-8065769 : OOM on Window/Solaris in test compile-octane-splitter.js
  • Type: Bug
  • Component: core-libs
  • Sub-Component: jdk.nashorn
  • Affected Version: 8u40,8u45,9
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: solaris,windows
  • CPU: generic
  • Submitted: 2014-11-24
  • Updated: 2015-06-04
  • Resolved: 2014-12-03
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
8u40Fixed 9 b42Fixed
Updated: added noreg-hard label as the problem which happens only intermittently and is hard to reproduce. However, the stack frames showing Deflater#init as problem spot are pretty strong evidence that this will fix the problem.

attached full log with stacktrace

[echo] run.test.jvmargs=-server -Dfile.encoding=UTF-8 -Duser.language=tr -Duser.country=TR -Dnashorn.typeInfo.cacheDir=build/test/type_info_cache -XX:+HeapDumpOnOutOfMemoryError -ea [echo] run.test.jvmargs.octane=-server -Dfile.encoding=UTF-8 -Duser.language=tr -Duser.country=TR -Dnashorn.typeInfo.cacheDir=build/test/type_info_cache -XX:+HeapDumpOnOutOfMemoryError -XX:TypeProfileLevel=222 [echo] run.test.xms=2G [echo] run.test.xmx=2G

What flags is this running with? I can run test/script/basic/compile-octane-splitter.js with -Xmx500m on Linux. It starts failing in mandreel.js with -Xmx400m. I've tried to reduce the memory requirements of Splitter, but didn't find anything I could do. Also, the OOM seems to occur in codegen (splitter increases the code that must be generated). Depending on what amount of heap the error occurs we should close this as WONTFIX (mandreel is a huge script, and we're compiling it with a very low splitter threshold here), or investigate further if the error occurs with higher heap sizes.