Open zp-stripe opened 10 months ago
Hi @zp-stripe,
Thank you for reporting the issue.
Could you please attach hs_err_*.log
file if you have them?
In the provided stack trace I see java.base@17.0.8.1
which mean Corretto 17.0.8. However in Platform information the specified version is 17.0.9.
Could you please check the crash happens on Corretto 17.0.9.8.1?
Thanks
I got that version from running java --version
as mentioned in the prompt:
zp@host:~$ java --version
openjdk 17.0.9 2023-10-17 LTS
OpenJDK Runtime Environment Corretto-17.0.9.8.1 (build 17.0.9+8-LTS)
OpenJDK 64-Bit Server VM Corretto-17.0.9.8.1 (build 17.0.9+8-LTS, mixed mode, sharing)
Here's another log snippet that confirms the version:
[2023-11-14 22:07:48.227082] # A fatal error has been detected by the Java Runtime Environment:
[2023-11-14 22:07:48.227090] #
[2023-11-14 22:07:48.227107] # SIGSEGV (0xb) at pc=0x0000000000000000, pid=2398, tid=4130
[2023-11-14 22:07:48.227114] #
[2023-11-14 22:07:48.227127] # JRE version: OpenJDK Runtime Environment Corretto-17.0.9.8.1 (17.0.9+8) (build 17.0.9+8-LTS)
[2023-11-14 22:07:48.227163] # Java VM: OpenJDK 64-Bit Server VM Corretto-17.0.9.8.1 (17.0.9+8-LTS, mixed mode, sharing, tiered, compressed class ptrs, g1 gc, linux-aarch64)
[2023-11-14 22:07:48.227172] # Problematic frame:
[2023-11-14 22:07:48.227180] # C 0xfffffffffffffffc
maybe the minor version changed recently, not sure.
I don't have an hs_err_
file on hand right now because the hosts were replaced, but I can try to get one soon when the problem reoccurs and I will attach it here. Thanks.
Here is the hs_err
file
@zp-stripe According to the hs_err
file, you are using Trino-414. On https://github.com/trinodb/trino I see the latest version is 433. Could you please check if the crash happens on the version 433?
The crashes you've reported are all on aarch64. Have you also observed them on x86_64 or are you running exclusively on aarch64?
We got SIGSEGV after upgrading to 17.0.9.8.1. Do you think it is relevant to this issue or async profiler issue which was supposed to be fixed with 17.0.9?
Unfortunately, I can not get the hs_err_pid1.log
.
[error occurred during error reporting (), id 0xb, SIGSEGV (0xb) at pc=0x00007f414ee0623b]
#
# https://github.com/corretto/corretto-17/issues/
# If you would like to submit a bug report, please visit:
#
# /tmp/hs_err_pid1.log
# An error report file with more information is saved as:
#
# The JFR repository may contain useful JFR files. Location: /tmp/2023_11_30_12_57_36_1
#
# Core dump will be written. Default location: Core dumps may be processed with "/usr/share/apport/apport -p%p -s%s -c%c -d%d -P%P -u%u -g%g -- %E" (or dumping to //core.1)
#
# V [libjvm.so+0x253889] forte_fill_call_trace_given_top(JavaThread*, ASGCT_CallTrace*, int, frame) [clone .isra.20]+0x15d
# Problematic frame:
# 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-amd64)
# JRE version: OpenJDK Runtime Environment Corretto-17.0.9.8.1 (17.0.9+8) (build 17.0.9+8-LTS)
#
# SIGSEGV (0xb) at pc=0x00007f414da20889, pid=1, tid=578
#
# A fatal error has been detected by the Java Runtime Environment:
#
Unfortunately, if that's the full output available and we don't have the hs_err, it's nearly impossible to say. That log doesn't specify where the crash occurred
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
A clear and concise description of what the bug is.
To Reproduce
Steps and (source) code to reproduce the behavior. Unable to reproduce consistently
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Platform information
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.