JDK-8038215 : Crash in register_method
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: hs25,9
  • Priority: P2
  • Status: Closed
  • Resolution: Cannot Reproduce
  • CPU: x86_64
  • Submitted: 2014-03-24
  • Updated: 2019-09-13
  • Resolved: 2014-05-05
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.
Related Reports
Relates :  
compiler/startup/SmallCodeCacheStartup.java crashes in register method

# A fatal error has been detected by the Java Runtime Environment:
#  SIGSEGV (0xb) at pc=0xffff80fc6be1e050, pid=21287, tid=55
# JRE version: Java(TM) SE Runtime Environment (8.0-b132) (build 1.8.0-fastdebug-b132)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.0-b62-internal-201403210232.vkozlov.8037915-fastdebug compiled mode solaris-amd64 compressed oops)
# Problematic frame:
# V  [libjvm.so+0xd4e050]  void ciEnv::register_method(ciMethod*,int,CodeOffsets*,int,CodeBuffer*,int,OopMapSet*,ExceptionHandlerTable*,ImplicitExceptionTable*,AbstractCompiler*,int,bool,bool,RTMState)+0xa9c
# Core dump written. Default location: /export/local/aurora/sandbox/results/workDir/compiler/startup/SmallCodeCacheStartup/core or core.21287
# If you would like to submit a bug report, please visit:
#   http://bugreport.sun.com/bugreport/crash.jsp

JDK-8040798 blocked investigating this issue, since the JVM deadlocked when executing the test a large amount of times. Now that JDK-8040798 is fixed, the bug is not reproducible after having the test executed 10000X plus times. Also the fix of JDK-8040798 could have fixed this issue, since the bug fixes an memory allocation/free bug of compile tasks. Please feel free to reopen the bug, if the same issue occurs again.

Another workaround is the reduce the number of compiler threads.