-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
occasional SIGSEGV #156
Comments
Hi @zp-stripe, Thanks |
I got that version from running
Here's another log snippet that confirms the version:
maybe the minor version changed recently, not sure. I don't have an |
Here is the |
@zp-stripe According to the |
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. Unfortunately, I can not get the
|
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 [email protected] 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.The text was updated successfully, but these errors were encountered: