JVM crash

[metodski]

Tracer Version(s)

1.49.0

Java Version(s)

21.0.7

JVM Vendor

Amazon Corretto

Bug Report

Our Java application running on Corretto 21.0.7.6.1 experienced a fatal JVM crash caused by a segmentation fault (SIGSEGV). It seems to occur randomly. The app is a short-lived microservice and a lot of instances are created and destroyed each day. It crashes very rarely maybe a few times a week.The application was running as a containerized Java process inside a Kubernetes cluster.
Datadog’s Java agent was in use.
We have not been able to reliably reproduce the issue, but it occurred during normal operation of our service.

I originally submitted this as a bug in the corretto tracker where Volker Simonis did some investigation on the issue.

hs_error_pid1 (1).log

Problematic frame:
V [libjvm.so+0x9249d0] JavaThread::is_interrupted(bool)+0x0
The crash happened in the context of a background thread named StatsD-Sender-1, part of the dogstatsd Java client.

Expected Behavior

The JVM should remain stable and not crash.

Reproduction Code

No response

[clemstoquart]

Hello dd team,

We have the same issue with the Tracer release 1.52, we just updated our apps to the 1.53 release so we'll see if it still happens.