Skip to content
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

Open
ravivegiraju opened this issue Jun 1, 2023 · 6 comments
Open

JVM Crash - Problematic frame:libjvm.so+0x79e743 #328

ravivegiraju opened this issue Jun 1, 2023 · 6 comments
Labels
bug Something isn't working

Comments

@ravivegiraju
Copy link

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.

@ravivegiraju ravivegiraju added the bug Something isn't working label Jun 1, 2023
@benty-amzn
Copy link
Contributor

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.

@ravivegiraju
Copy link
Author

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.
hs_err_pid14980.jfr.zip

@apangin
Copy link

apangin commented Jun 2, 2023

Hi @ravivegiraju, the crash happens in AsyncGetCallTrace - the JVM entry used by profilers, in your case - Datadog profiler.

I know two issues with AsyncGetCallTrace that are likely related to your problem - JDK-8297967 and JDK-8282306. The latter one has been already fixed in 11.0.18, so updating JDK may help.

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.

@ravivegiraju
Copy link
Author

Thank You @apangin. We are planning on upgrading to 11.0.19 as suggested by @benty-amzn

@vsurathu
Copy link

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
Core dump will be written. Default location: //core.xx

@wajdiAbdelkariem
Copy link

hs_err_pid11167.log
Hi, we got the same error different Problematic Frame "libjvm.so+0x79dc4d"and with Corretto-11.0.18.10.1. should that be considered the same bug? or create new one?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

5 participants