-
-
Notifications
You must be signed in to change notification settings - Fork 15
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
SIGSEV on ObjectSynchronizer::FastHashCode #831
Comments
@svenrienstra This is coming from the elastic APM agent. Are you able to remove that and see if the crash still occurs? |
@karianna we've already disabled the specific instrumentation which caused it ( |
Ok - those agents tend to byte code weave or call lower level stacks so compiler crashes can occur. I'd also report it to them |
Also see #775 |
Thanks @karianna, I'll follow that as well, although we're not using ZGC but G1. I've also openend a ticket with Elastic: https://discuss.elastic.co/t/jvm-crash-originating-from-apm-agent/337265 |
We are marking this issue as stale because it has not been updated for a while. This is just a way to keep the support issues queue manageable. |
Please provide a brief summary of the bug
We've now multiple times experienced a JVM crash in our cluster. We haven't been able to establish a pattern of when this happens or what triggers this. We get the following crash:
hs_err_pid1.log
Please provide steps to reproduce where possible
I've not been able to reproduce this manually.
Expected Results
A graceful exception, not the whole JVM to crash.
Actual Results
JVM crash
What Java Version are you using?
eclipse-temurin:17-alpine docker image
What is your operating system and platform?
eclipse-temurin:17-alpine running on Kubernetes cluster
How did you install Java?
No response
Did it work before?
No response
Did you test with the latest update version?
No response
Did you test with other Java versions?
No response
Relevant log output
The text was updated successfully, but these errors were encountered: