JDK-8208235 : mlvm/meth/stress/jni/nativeAndMH/Test.java timed out
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 11,12
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • OS: solaris
  • CPU: sparc
  • Submitted: 2018-07-25
  • Updated: 2019-01-31
  • Resolved: 2019-01-31
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.
Other
tbdResolved
Related Reports
Duplicate :  
JDK-8209763 - vmTestbase/vm/mlvm/meth/stress/jni/nativeAndMH/Test.java time out
Duplicate :  
JDK-8058176 - [mlvm] tests should not allow code cache exhaustion
Relates :  
JDK-8193082 - vmTestbase/vm/mlvm/meth/stress/jni/nativeAndMH/Test.java failed in PIT w/ ERROR at nativeAndMH.c:51
Description
The mlvm/meth/stress/jni/nativeAndMH/Test.java test timed out on Solaris/Sparc during an ad hoc hs-tier6 and hs-tier7 testing with CDS enabled.
Comments
closing as dup of JDK-8058176 [mlvm] tests should tolerate exceptions caused by code cache exhaustion
31-01-2019
One in previous failed testing was also dine with switched off Tiered compilation and had CodeCache full too. And other test ran with Tiered on but it is also run out of space: Java HotSpot(TM) 64-Bit Server VM warning: CodeHeap 'profiled nmethods' is full. Compiler has been disabled. Java HotSpot(TM) 64-Bit Server VM warning: Try increasing the code heap size using -XX:ProfiledCodeHeapSize= In all cases Compilation was disable and test run in Interpreter cause timeout I think. It would be interesting to see how long test takes running with -Xint if it is possible. I don't see @requires or checks in the test which would limit it to run only with JIT. Test have to be adjusted to run in Interpreter in reasonable time. Filled up CodeCache is definitely an issuie and needs to be investigated too.
13-08-2018
interestingly enough, 'CodeCache is full. Compiler has been disabled. ' tend to be a forerunner of NSME and VME in this test -- JDK-8193082, but in all the failures mentioned here the test didn't fail w/ Errors, but timed out instead.
13-08-2018
Last testing added by Mikael was done with "deadly" flags combination: -Xcomp -server -XX:-TieredCompilation -XX:+DeoptimizeALot Because Tierd is off CodeCache size was reduced to default 48Mb and it seems it was not enough for this test and compiler was disabled: [342.104s][warning][codecache] CodeCache is full. Compiler has been disabled. [342.104s][warning][codecache] Try increasing the code cache size using -XX:ReservedCodeCacheSize= CodeCache: size=49152Kb used=42244Kb max_used=42244Kb free=6907Kb bounds [0xffffffff6dc00000, 0xffffffff70c00000, 0xffffffff70c00000] total_blobs=75802 nmethods=24314 adapters=837 compilation: disabled (not enough contiguous free space left) stopped_count=1, restarted_count=0
13-08-2018
ILW = Test times out (probably test bug), single test on slow machines with CDS, no workaround = MLH = P4
26-07-2018