Has anyone encountered a similar problem?
Can it be caused by HikariCP? (Happened to applications that used versions HikariCP v. 2.7.8 and 3.4.1)
#
# A fatal error has been detected by the Java Runtime Environment:
#
# Internal Error (output.cpp:1593), pid=17180, tid=0x0000000000000025
# guarantee((int)(blk_starts[i+1] - blk_starts[i]) >= (current_offset - blk_offset)) failed: shouldn't increase block size
#
# JRE version: Java(TM) SE Runtime Environment (8.0_121-b13) (build 1.8.0_121-b13)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.121-b13 mixed mode solaris-sparc compressed oops)
# Core dump written. Default location: /pub/var/is2_3/log/core or core.17180
#
# If you would like to submit a bug report, please visit:
# http://bugreport.java.com/bugreport/crash.jsp
#
--------------- T H R E A D ---------------
Current thread (0x0000000100f1f000): JavaThread "C2 CompilerThread5" daemon [_thread_in_native, id=37, stack(0xffffffff50100000,0xffffffff50200000)]
Stack: [0xffffffff50100000,0xffffffff50200000], sp=0xffffffff501fc190, free space=1008k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
V [libjvm.so+0xded044] void VMError::report_and_die()+0x6dc
V [libjvm.so+0x537a90] void report_vm_error(const char*,int,const char*,const char*)+0x60
V [libjvm.so+0xb938c4] void Compile::fill_buffer(CodeBuffer*,unsigned*)+0x121c
V [libjvm.so+0x4c2744] void Compile::Code_Gen()+0x4a8
V [libjvm.so+0x4bb6e8] Compile::Compile(ciEnv*,C2Compiler*,ciMethod*,int,bool,bool,bool)+0x12b8
V [libjvm.so+0x3b73b0] void C2Compiler::compile_method(ciEnv*,ciMethod*,int)+0xa8
V [libjvm.so+0x4d347c] void CompileBroker::invoke_compiler_on_method(CompileTask*)+0xa64
V [libjvm.so+0x4d2330] void CompileBroker::compiler_thread_loop()+0x3d8
V [libjvm.so+0xd36fa4] void JavaThread::thread_main_inner()+0xf4
V [libjvm.so+0xd36e90] void JavaThread::run()+0x320
V [libjvm.so+0xb75f58] java_start+0x390
C [libc.so.1+0x149884] _lwp_start+0x8
Current CompileTask:
C2:19733459 27115 ! 4 com.zaxxer.hikari.util.ConcurrentBag::borrow (295 bytes)
Has anyone encountered a similar problem? Can it be caused by HikariCP? (Happened to applications that used versions HikariCP v. 2.7.8 and 3.4.1)
hs_err_pid17180.log