JDK-8230299 : runtime/cds/SpaceUtilizationCheck.java timesout with StackOverflowError with -Xcomp
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 14
  • Priority: P4
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2019-08-28
  • Updated: 2019-08-30
  • Resolved: 2019-08-30
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.
JDK 14
14Resolved
Related Reports
Duplicate :  
Description
Run Test - runtime/cds/SpaceUtilizationCheck.java
   in linux-x64-debug with 
-Xcomp -XX:+CreateCoredumpOnCrash -ea -esa -XX:CompileThreshold=100 -XX:+UnlockExperimentalVMOptions -server -XX:+TieredCompilation -XX:-UseBiasedLocking

[extracts from Test log]
.................
[2019-08-28T02:54:00.412229Z] Gathering output for process 31690
[ELAPSED: 4598 ms]
[logging stdout to SpaceUtilizationCheck-0000-dump.stdout]
[logging stderr to SpaceUtilizationCheck-0000-dump.stderr]
[STDERR]

[2019-08-28T02:54:03.955300Z] Waiting for completion for process 31690
Timeout refired 1200 times
----------System.err:(14/1203)----------
Exception in thread "process reaper" java.lang.StackOverflowError
	at java.base/java.util.concurrent.ConcurrentHashMap.fullAddCount(ConcurrentHashMap.java:2576)
..........................
Comments
Closing this as duplicate of JDK-8217475 (this is not a compiler issue as the same failure happens with -Xint, see JDK-8222441).
30-08-2019

By default process reaper threads only have a 128K stack and this should be sufficient for them. The stacktrace doesn't show anything interesting: Exception in thread "process reaper" java.lang.StackOverflowError at java.base/java.util.concurrent.ConcurrentHashMap.fullAddCount(ConcurrentHashMap.java:2576) at java.base/java.util.concurrent.ConcurrentHashMap.addCount(ConcurrentHashMap.java:2326) at java.base/java.util.concurrent.ConcurrentHashMap.putVal(ConcurrentHashMap.java:1075) at java.base/java.util.concurrent.ConcurrentHashMap.putIfAbsent(ConcurrentHashMap.java:1541) at java.base/java.lang.invoke.MethodType$ConcurrentWeakInternSet.add(MethodType.java:1380) at java.base/java.lang.invoke.MethodType.makeImpl(MethodType.java:327) at java.base/java.lang.invoke.MethodHandleNatives.findMethodHandleType(MethodHandleNatives.java:377) at java.base/java.util.concurrent.CompletableFuture.completeValue(CompletableFuture.java:305) at java.base/java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:2143) at java.base/java.lang.ProcessHandleImpl$1.run(ProcessHandleImpl.java:162) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:830) but there may be hidden frames, or native frames contributing to the problem. If this is a repeatable issue then it may be necessary to run the test with the default stack size: -Djdk.lang.processReaperUseDefaultStackSize=false
28-08-2019