-
Notifications
You must be signed in to change notification settings - Fork 21
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
Fatal Error In Runtime At Pc = 0x00007f8de4080028 #72
Comments
Facing same issue : |
@ved-asole yours is not the same issue, you are seeing a crash in |
@olivergillespie Thanks for confirming |
I think that instruction around here, most likely the AVX one,
Given:
...I would suspect there is a problem with KVM/Docker configuration? Although I am seeing that AVX flags are passed "well":
Please check your virtualization config. |
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.
I was running a Minecraft server and a fatal java runtime error occurred.
To Reproduce
Steps and (source) code to reproduce the behavior.
Unknown.
Platform information
It was my own server on a KVM instance inside a docker container. The version of java was 21 and the hardware was 4 AMD 7950x cores.
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_pid1.log
The text was updated successfully, but these errors were encountered: