-
Notifications
You must be signed in to change notification settings - Fork 290
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
dd-trace-java v1.11.0 crashes the JVM #4978
Comments
We are seeing similar with Java 11 + CentOS. Identical application instances with version 1.10.0~c545cdc5a3 do not experience this issue.
|
Seeing the same issue with Temurin base image and Java 11.0.18. |
Just in case people haven't seen the workaround Jaroslav posted on slack:
|
We are validating the fix now and will do a patch release once we are sure the root cause is fixed. |
Also experienced this today: Problematic frame: |
Fixed by #4981 |
1.11.1 didn't solve the issue for us
|
+1 to above
instead of
|
Thank you, but this does not seem to be working yet. we are on Java 8. it still crashes with the latest agent. SIGSEGV (0xb) at pc=0x00007fc0f07a28b2, pid=45, tid=0x00007fc078b5f700 |
+1 to not fixed, experiencing the same crash on 1.11.1 |
We acknowledge that this crash is still possible, hence reopening the issue, and are working on getting 1.11.2 out with full mitigation. |
We managed to reproduce the issue and verified a fix for this, released in 1.11.2. If the crash persists after upgrading to 1.11.2, please report back with the backtrace from the hs_err file, the JDK version and the base docker base image being used (or the linux and libc versions otherwise). |
1.11.2 has resolved this for me. Thank you. |
We encountered the same problem。。。。error just like above |
Hi @ahululu could you provide more details please?
|
|
Hi @ahululu - this is indeed a JVM crash, but not related to this issue, and it doesn't look like this could be caused by the profiler. It may help if you post this info to the other crash report you are commenting on. |
Our server automatically downloaded the latest trace agent. v1.11.0
After a few minutes, our servers started to crash and reboot in loop. After some investigation, it seems that the JVM was crashing. So maybe it's more a JVM issue, but it seems to be your recent changes that introduced this behaviour.
The text was updated successfully, but these errors were encountered: