Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

JVM crash

Open
#9,167 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
java, kubernetes
Domain
observability-sre

Research direction

Start by reading hs_error_pid1 (1).log and the investigation in Corretto issue 105, focusing on the JavaThread::is_interrupted crash frame and the StatsD-Sender-1 context. There is no reproduction code or repository file named in the report; done would require identifying an actionable cause or a reliably reproducible failure involving the Java agent and JVM.

Written by the indexing model from the issue text.

Description

type: bug report
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

Dominant language
Java
Stars
737
Forks
361
Avg merge
3d 20h
Merged PRs (30d)
173

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DataDog/dd-trace-java

All issues in DataDog/dd-trace-java

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.