JDK-8159412 : Our company recently upgraded from JDK 1.7 to JDK 1.8.0_25, and have experienced fatal errors at least once per week.
  • Type: Bug
  • Component: hotspot
  • Sub-Component: compiler
  • Affected Version: 8u25
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: linux
  • CPU: x86_64
  • Submitted: 2016-06-14
  • Updated: 2016-06-14
  • Resolved: 2016-06-14
Related Reports
Duplicate :  
Description
FULL PRODUCT VERSION :
JDK 1.8.0_25

FULL OS VERSION :
Linux  64 bit

EXTRA RELEVANT SYSTEM CONFIGURATION :
Java web module deployed on Tomcat 8, residing on a Linux 64 bit operating system

A DESCRIPTION OF THE PROBLEM :
We experience this fatal error at various times.

SIGSEGV (0xb) at pc=0x00007fcca8048e2f, pid=28326, 
> tid=140515957798656 # # JRE version: Java(TM) SE Runtime Environment 
> (8.0_25-b17) (build 1.8.0_25-b17) # Java VM: Java HotSpot(TM) 64-Bit 
> Server VM (25.25-b02 mixed mode linux-amd64 compressed oops) # 
> Problematic frame:
> # V  [libjvm.so+0x42be2f]  
> ciObjectFactory::create_new_object(Metadata*)+0x2f
> #
> # Failed to write core dump. Core dumps have been disabled. 

I have read other users experiencing this issue, and I believe this could be fixed in a later version of the JDK (JDK-8060147)

http://bugs.java.com/view_bug.do?bug_id=8060147

JDK-8060147 : SIGSEGV in Metadata::mark_on_stack() while marking metadata in ciEnv.


Code fix here?

ciMetadata* create_new_object(Metadata* o);
+  ciMetadata* create_new_metadata(Metadata* o);

http://hg.openjdk.java.net/jdk8u/jdk8u/hotspot/rev/6a528388c7da

Can someone confirm which version of the JDK 8 is stable and resolves this issue please ?


THE PROBLEM WAS REPRODUCIBLE WITH -Xint FLAG: Did not try

THE PROBLEM WAS REPRODUCIBLE WITH -server FLAG: Did not try

REGRESSION.  Last worked in version 7u80

ERROR MESSAGES/STACK TRACES THAT OCCUR :
> [root@buvlin01-bsgtom ~]# tail -30 /opt/tomcat/logs/catalina.out [GC 
> (Allocation Failure)  1197450K->788454K(2044736K), 0.0705100 secs] [GC 
> (Allocation Failure)  1207910K->796272K(2044736K), 0.0760419 secs] [GC 
> (Allocation Failure)  1215728K->806256K(2044736K), 0.0895953 secs] [GC 
> (Allocation Failure)  1225712K->822118K(2044736K), 0.1192428 secs] [GC 
> (Allocation Failure)  1241574K->810018K(2044736K), 0.1334727 secs] [GC 
> (Allocation Failure)  1229474K->831095K(2044736K), 0.1229355 secs] [GC 
> (Allocation Failure)  1250551K->820291K(2044736K), 0.1239883 secs] [GC 
> (CMS Initial Mark)  828664K(2044736K), 0.0460803 secs] [GC (CMS Final 
> Remark)  1022457K(2044736K), 0.5761958 secs] # # A fatal error has 
> been detected by the Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0x00007fcca8048e2f, pid=28326, 
> tid=140515957798656 # # JRE version: Java(TM) SE Runtime Environment 
> (8.0_25-b17) (build 1.8.0_25-b17) # Java VM: Java HotSpot(TM) 64-Bit 
> Server VM (25.25-b02 mixed mode linux-amd64 compressed oops) # 
> Problematic frame:
> # V  [libjvm.so+0x42be2f]  
> ciObjectFactory::create_new_object(Metadata*)+0x2f
> #
> # Failed to write core dump. Core dumps have been disabled. To enable 
> core dumping, try "ulimit -c unlimited" before starting Java again # # 
> An error report file with more information is saved as:
> # /tmp/hs_err_pid28326.log


REPRODUCIBILITY :
This bug can be reproduced occasionally.


Comments
This is already known issue JDK-8060147, It is been fixed in 9 and backported to 8u40. Please update your java to 8u40 or the later versions to get away with this issue.
14-06-2016