benty-amzn
commented
5 days ago Hi, thanks for contacting us about this. A few questions to help us investigate
- Does the issue only occur on aarch64 / graviton hosts?
- Is there any behavior that seems to trigger the crash, or it just happens rarely and randomly after a deployment?
- Has the crash happened with any version other than 17.0.9+8? That release is about a year old now, and the crash may be fixed in a newer release
maroraFundrise
Thank you for taking the time to help improve OpenJDK and Corretto.
If your request concerns a security vulnerability then please report it by email to aws-security@amazon.com instead of here. (You can find more information regarding security issues at https://aws.amazon.com/security/vulnerability-reporting/.)
Otherwise, if your issue concerns OpenJDK and is not specific to Corretto we ask that you raise it to the OpenJDK community. Depending on your contributor status for OpenJDK, please use the JDK bug system or the appropriate mailing list for the given problem area or update project.
If your issue is specific to Corretto, then you are in the right place. Please proceed with the following.
Describe the bug
After moving to graviton instances and upgrading to corretto-17 we have seen occasional JVM crashes with the following SIGSEV error.
Frequency: 4 times since September 2024, Usually happens 1-2 hours after the deployment. Until the crash, workload runs fine.
I have jfr, logs and a coredump as well. Let me know if I can provide any additional information. After analyzing these logs, we can confirm that application was not running out of memory and there were no deadlocks.
#
A fatal error has been detected by the Java Runtime Environment:
#
SIGSEGV (0xb) at pc=0x0000ffffa6f71a58, pid=2217677, tid=2217917
#
JRE version: OpenJDK Runtime Environment Corretto-17.0.9.8.1 (17.0.9+8) (build 17.0.9+8-LTS)
Java VM: OpenJDK 64-Bit Server VM Corretto-17.0.9.8.1 (17.0.9+8-LTS, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-aarch64)
Problematic frame:
V [libjvm.so+0x571a58] ClassFileParser::parse_methods(ClassFileStream const, bool, AccessFlags, bool, bool, JavaThread*)+0x270
#
Core dump will be written. Default location: Core dumps may be processed with "/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h" (or dumping to [REDACTED]/core.2217677)
#
JFR recording file will be written. Location: [REDACTED]/hs_err_pid2217677.jfr
#
If you would like to submit a bug report, please visit:
https://github.com/corretto/corretto-17/issues/
#
#
A fatal error has been detected by the Java Runtime Environment:
#
SIGSEGV (0xb) at pc=0x0000ffff8b662e4c, pid=1036123, tid=1036261
#
JRE version: OpenJDK Runtime Environment Corretto-17.0.9.8.1 (17.0.9+8) (build 17.0.9+8-LTS)
Java VM: OpenJDK 64-Bit Server VM Corretto-17.0.9.8.1 (17.0.9+8-LTS, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, linux-aarch64)
Problematic frame:
C [libc.so.6+0x32e4c] __GI___memcpy_sve+0xcc
#
Core dump will be written. Default location: /opt/core.%e.1036123 (max size 4000000 kB). To ensure a full core dump, try "ulimit -c unlimited" before starting Java again
#
JFR recording file will be written. Location: [REDACTED]/hs_err_pid1036123.jfr
To Reproduce
Unable to reproduce consistently
Expected behavior
JVM should not crash
Screenshots
If applicable, add screenshots to help explain your problem.
Platform information
Host: AArch64, 4 cores, 15G, Amazon Linux release 2023 (Amazon Linux) on EC2. JRE version: OpenJDK Runtime Environment Corretto-17.0.9.8.1
Additional context
Add any other context about the problem here.
For VM crashes, please attach the error report file. By default the file name is
hs_err_pidpid.log, where pid is the process ID of the process. hs_err_pid1036123-redacted.log