Bump java-profiler (ddprof) to 1.49.0

[jbachorik]

What Does This Do

Bumps the bundled java-profiler (ddprof) native library dependency from 1.48.1 to 1.49.0.

Motivation

Pick up the latest upstream ddprof release, including reliability and crash-safety fixes.

Additional Notes

Most significant changes/fixes in ddprof 1.49.0:

• Missing libgcc_s.so.1 on the host no longer causes a crash — DataDog/java-profiler#689, DataDog/java-profiler#720 (Alpine/musl)
• Avoid retaining invalid VM method pointers — DataDog/java-profiler#699
• Guard Profiler::recordSample() stack walk against faults — DataDog/java-profiler#687
• Guard Recording::writeElement against SIGSEGV on a corrupted metadata tree — DataDog/java-profiler#692
• Fix memory leak in JfrMetadata::reset() — DataDog/java-profiler#694
• Remove legacy DirectByteBuffer-based OTEP context storage (Phase 3) — DataDog/java-profiler#696
• Never patch the profiler's own import table — DataDog/java-profiler#721

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors
• Once approved, use merge queue to merge the PR

[datadog-datadog-us1-prod]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 57.94% (-0.04%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 0d4cd3a | Docs | Datadog PR Page | Give us feedback!}

[dd-octo-sts]

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	14.09 s	13.93 s	[+0.0%; +2.2%] (maybe worse)
startup:insecure-bank:tracing:Agent	12.94 s	12.99 s	[-0.9%; +0.2%] (no difference)
startup:petclinic:appsec:Agent	16.85 s	16.64 s	[+0.4%; +2.1%] (maybe worse)
startup:petclinic:iast:Agent	16.35 s	16.91 s	[-7.5%; +0.9%] (no difference)
startup:petclinic:profiling:Agent	16.33 s	16.71 s	[-6.7%; +2.1%] (no difference)
startup:petclinic:sca:Agent	16.67 s	16.03 s	[-0.4%; +8.4%] (no difference)
startup:petclinic:tracing:Agent	16.10 s	16.27 s	[-1.7%; -0.4%] (maybe better)

Commit:0d4cd3a1 · CI Pipeline · Benchmarking Platform UI

---

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.

[datadog-datadog-us1-prod]

More details

The 1.49.0 artifact preserved native load/error handling, context publication, JVM access, and parsed JFR output across restart, with Java 8 and 21 coverage. All four Linux native variants remained packaged, and upstream legacy API removals have no repository consumers.

Was this helpful? React 👍 or 👎

_{📊 Validated against 9 scenarios · Open Bits AI session}

_{🤖 Datadog Autotest · Commit 0d4cd3a · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest}

[jbachorik]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-08-10 06:13:11 UTC ℹ️ Start processing command /merge

---

2026-08-10 06:13:17 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 2h (p90).

---

2026-08-10 07:02:29 UTC ℹ️ MergeQueue: This merge request was merged