-
Notifications
You must be signed in to change notification settings - Fork 107
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
JVM Crash - Problematic frame:libjvm.so+0x79e743 #328
Comments
Thanks for contacting us about this, we're looking into it. It looks like you're running on Corretto 11.0.17, which is 2 releases behind the current 11.0.19. It's possible this issue has already been fixed in a newer release, however without a reproducer it will be difficult to validate. This issue appears to be related to profiling, and I see flags for JFR and datadog in your command line arguments. Are you running with these flags consistently? If not, it may help reproduce the issue if you enable them. |
Thanks @benty-amzn for a quick response on this. We have currently disabled the profiling and will not be able to enable this again. And we hope the JVM never crashed again. If you can help answer one question, that would be, what is the error from the crash? Like is it stack overflow error or out of memory error etc. I have a core dump corresponding to this issue that I analyzed but did not find anything that is suspicious. Attached the core dump if you are interested in taking a look. Thanks again for you time. |
Hi @ravivegiraju, the crash happens in I know two issues with I implemented a workaround for a similar issue in async-profiler. However, I'm not sure if Datadog profiler has all up-to-date fixes from async-profiler - it's better to check with them directly. |
Thank You @apangin. We are planning on upgrading to 11.0.19 as suggested by @benty-amzn |
Hi, we are on Corretto 11.0.19.17.1 seeing a similar error. Unfortunately, the dump was not available as the process got restarted and we lost the file. Is this a known issue? VM are crashed with below error : A fatal error has been detected by the Java Runtime Environment:SIGSEGV (0xb) at pc=0x00007f988916e9c3, pid=xx, tid=619809 JRE version: OpenJDK Runtime Environment Corretto-11.0.19.7.1 (11.0.19+7) (build 11.0.19+7-LTS) Java VM: OpenJDK 64-Bit Server VM Corretto-11.0.19.7.1 (11.0.19+7-LTS, mixed mode, tiered, g1 gc, linux-amd64) Problematic frame:V [libjvm.so+0x7a19c3] frame::is_interpreted_frame_valid(JavaThread*) const+0x43 |
hs_err_pid11167.log |
hs_err_pid14980.log
Thank you for taking the time to help improve OpenJDK and Corretto 11.
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 11 and is not specific to Corretto 11 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 11, then you are in the right place. Please proceed with the following.
Describe the bug
JVM has crashed abruptly without a meaningful error message
To Reproduce
Issue happened only once so far and I do not yet have any steps to reproduce.
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
JRE version: OpenJDK Runtime Environment Corretto-11.0.17.8.1 (11.0.17+8) (build 11.0.17+8-LTS)
hs_err_pid14980.log
Java VM: OpenJDK 64-Bit Server VM Corretto-11.0.17.8.1 (11.0.17+8-LTS, mixed mode, tiered, compressed oops, g1 gc, linux-amd64)
Look into the attached error file for more details.
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: