our server crashed leaving this behind - I stripped a bit of info away <<>> marks the spots:
#
# A fatal error has been detected by the Java Runtime Environment:
#
# SIGSEGV (0xb) at pc=0x00007f5f185a04b1, pid=3329, tid=3343
#
# JRE version: OpenJDK Runtime Environment Corretto-17.0.0.35.1 (17.0+35) (build 17+35-LTS)
# Java VM: OpenJDK 64-Bit Server VM Corretto-17.0.0.35.1 (17+35-LTS, mixed mode, sharing, tiered, compressed class ptrs, z gc, linux-amd64)
# Problematic frame:
# C [libc.so.6+0x14b4b1] __strlen_avx2+0x11
#
# No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# If you would like to submit a bug report, please visit:
# https://github.com/corretto/corretto-17/issues/
#
--------------- S U M M A R Y ------------
Command Line: <<<stripped>>> -XX:+UnlockExperimentalVMOptions -XX:+UseZGC -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=/tmp -XX:+PrintCommandLineFlags -XX:+DisableExplicitGC -XX:ZCollectionInterval=20 -Xlog:safepoint=info,compilation*,jit*,gc:file=<<<stripped>>>/logs/jit-logging-output.log:time,level,tags:filecount=10,filesize=10M -XX:+PrintCompilation -XX:+SafepointTimeout -XX:SafepointTimeoutDelay=30 -XX:+UseCountedLoopSafepoints -XX:LoopStripMiningIter=10 -Xmx11G -Xms11G -XX:ThreadPriorityPolicy=1 <<<stripped>>>
Host: Intel(R) Xeon(R) Platinum 8124M CPU @ 3.00GHz, 8 cores, 15G, Amazon Linux release 2 (Karoo)
Time: Tue Oct 26 12:51:25 2021 UTC elapsed time: 26381.405019 seconds (0d 7h 19m 41s)
--------------- T H R E A D ---------------
Current thread (0x00007f5f10089f90): VMThread "VM Thread" [stack: 0x00007f5ef80e6000,0x00007f5ef81e6000] [id=3343]
Stack: [0x00007f5ef80e6000,0x00007f5ef81e6000], sp=0x00007f5ef81e3ee8, free space=1015k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [libc.so.6+0x14b4b1] __strlen_avx2+0x11
V [libjvm.so+0x915e84] jio_fprintf+0x84
V [libjvm.so+0xaa2fa1] LogFileStreamOutput::write(LogDecorations const&, char const*)+0xa1
V [libjvm.so+0xaa20cc] LogFileOutput::write(LogDecorations const&, char const*)+0x7c
V [libjvm.so+0xaaf34f] LogTagSet::vwrite(LogLevel::type, char const*, __va_list_tag*)+0x21f
V [libjvm.so+0xcf8aaa] void LogImpl<(LogTag::type)119, (LogTag::type)0, (LogTag::type)0, (LogTag::type)0, (LogTag::type)0, (LogTag::type)0>::write<(LogLevel::type)3>(char const*, ...)+0x9a
V [libjvm.so+0xcf78de] SafepointTracing::end()+0xae
V [libjvm.so+0xcf7a48] SafepointSynchronize::end()+0x148
V [libjvm.so+0xf8ee4e] VMThread::inner_execute(VM_Operation*)+0x1ee
V [libjvm.so+0xf8f10f] VMThread::run()+0xbf
V [libjvm.so+0xf0bca2] Thread::call_run()+0xe2
V [libjvm.so+0xc44e71] thread_native_entry(Thread*)+0xe1
siginfo: si_signo: 11 (SIGSEGV), si_code: 1 (SEGV_MAPERR), si_addr: 0x000000000000001c
<<<stripped many more details>>>
This happened now once in one of the about 500 servers or so running the same code in different AWS regions over the last week or so.