JDK-8040798 : compiler/startup/SmallCodeCacheStartup.java timed out in RT_Baseline
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: hs25,9
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2014-04-17
  • Updated: 2023-07-21
  • Resolved: 2014-04-29
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 8 JDK 9
8u40Fixed 9 b14Fixed
Related Reports
Duplicate :  
JDK-8055420 - SIGSEGV in CompileQueue::delete_all during compiler's shutdown
Duplicate :  
JDK-8040805 - compiler/startup/SmallCodeCacheStartup.java can deadlock
Relates :  
JDK-8042570 - Excessive number of tests timing out on nightly testing due to fix for 8040798
Relates :  
JDK-8038215 - Crash in register_method
Description
    Timed out on Solaris x64 after 16 minutes. No further information is available in the log.
  
    Host: vm-v20z-4, AMD x86 2390 MHz, 2 cores, 4G, Solaris / Solaris 10, i86pc
    Options: -server -Xmixed -XX:MaxRAMFraction=8 -XX:+CreateMinidumpOnCrash -XX:+IgnoreUnrecognizedVMOptions -XX:-UseCompressedOops -XX:ReservedCodeCacheSize=256M
Comments
URL: http://hg.openjdk.java.net/jdk9/jdk9/hotspot/rev/48c15b47a4f1 User: lana Date: 2014-05-21 18:41:38 +0000
21-05-2014
URL: http://hg.openjdk.java.net/jdk9/hs-comp/hotspot/rev/48c15b47a4f1 User: anoll Date: 2014-04-29 07:14:10 +0000
29-04-2014
8040798: ILW=deadlock;very very odd config;no=MLH=>P4 // 8040805 is closed as a dup of 8040798
22-04-2014
JDK-8040805, Albert Noll: Reason: The test starts the JVM with 3m code cache and 64 compiler threads. As a result, it is very likely that not all compiler threads can be started due to insufficient space in the code cache. It is also possible that the initialization of all compiler threads of a particular compiler (C1/C2) fails. Since the test starts the JVM with -Xcomp (blocking compilation) the JVM waits forever for the compilation to complete. However, the compilation cannot complete, since there is no compiler thread to process the task.
22-04-2014