JDK-7000497 : G1: SIGSEGV in java.lang.ref.Finalizer$1.(Ljava/lang/Runnable;)V+0
  • Type: Bug
  • Component: hotspot
  • Sub-Component: gc
  • Affected Version: hs19
  • Priority: P3
  • Status: Closed
  • Resolution: Cannot Reproduce
  • OS: generic
  • CPU: generic
  • Submitted: 2010-11-16
  • Updated: 2013-09-18
  • Resolved: 2011-01-26
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 7
7Resolved
Related Reports
Relates :  
Relates :  
Relates :  
Description
Application crashes after 1.5 hours (HS 19 b09, server -XX:+UseCompressedOops -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:+DoEscapeAnalysis -XX:+IgnoreUnrecognizedVMOptions -XX:+UseCodeCacheFlushing):

# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f697f86b4fc, pid=4826, tid=140090380634384
...
# Problematic frame:
# j  java.lang.ref.Finalizer$1.<init>(Ljava/lang/Runnable;)V+0


Stack: [0x00007f69554fc000,0x00007f69555fd000],  sp=0x00007f69555faf78,  free space=1019k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
j  java.lang.ref.Finalizer$1.<init>(Ljava/lang/Runnable;)V+0
j  java.lang.ref.Finalizer.forkSecondaryFinalizer(Ljava/lang/Runnable;)V+5
j  java.lang.ref.Finalizer.runFinalization()V+7
v  ~StubRoutines::call_stub
V  [libjvm.so+0x40a16f];;  JavaCalls::call_helper(JavaValue*, methodHandle*, JavaCallArguments*, Thread*)+0x1df
V  [libjvm.so+0x622b89];;  os::os_exception_wrapper(void (*)(JavaValue*, methodHandle*, JavaCallArguments*, Thread*), JavaValue*, methodHandle*, JavaCallArguments*, Thread*)+0x19
V  [libjvm.so+0x409f85];;  JavaCalls::call(JavaValue*, methodHandle, JavaCallArguments*, Thread*)+0x25
V  [libjvm.so+0x443d17];;  jni_invoke_static(JNIEnv_*, JavaValue*, _jobject*, JNICallType, _jmethodID*, JNI_ArgumentPusher*, Thread*)+0x147
V  [libjvm.so+0x431ee0];;  jni_CallStaticVoidMethod+0x1f0

Java Threads: ( => current thread )
=>0x00007f695b855800 JavaThread "BenchmarkThread derby 2" [_thread_in_Java, id=8341, stack(0x00007f69554fc000,0x00007f69555fd000)]

Comments
EVALUATION I have been unable to reproduce the original problem but believe it is related to running out of perm space (at least according to the core file and hs_err file). Runs of the KitchenSink big app with the default perm sizes show OOME Perm Space messages. When the MaxPermSpace is increased to 256m 3 entire runs of the KitchenSink (with no perm space being depleted messages) were successfully completed. Closing as unreproducible.
26-01-2011