Bump java-profiler (ddprof) to 1.48.0

[kaahos]

What Does This Do

Bumps java-profiler (ddprof) from 1.47.0 to 1.48.0.

Motivation

Noticeable changes

• Add native malloc/socket stack capture with profiler-hook frame skipping by @jbachorik in feat(profiler): native malloc/socket stack capture with profiler-hook frame skipping java-profiler#648
• Add categorized native-memory accounting by @rkennke in feat(nativemem): categorized native-memory accounting — first cut java-profiler#669
• Set up signal handlers before initializing VMStructs and protect VMFlag::name() calls by @zhengyu123 in [fault-injection] Startup should setup signal handlers before initializing VMStructs and protect VMFlag::name() call java-profiler#674
• Make CodeCache memoryUsage() accurate and live by @rkennke in fix(codecache): make memoryUsage() accurate and live java-profiler#677
• Report the actual runtime-stubs cache size by @rkennke in fix(codecache): report the real runtime-stubs cache size java-profiler#681
• Use sigsetjmp/siglongjmp instead of setjmp/longjmp by @zhengyu123 in Use sigsetjmp/siglongjmp instead of setjmp/longjmp java-profiler#686

See the full release notes.

Additional Notes

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

Jira ticket: [PROJ-IDENT]

[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.02 s	14.03 s	[-0.9%; +0.8%] (no difference)
startup:insecure-bank:tracing:Agent	12.98 s	13.03 s	[-1.3%; +0.5%] (no difference)
startup:petclinic:appsec:Agent	16.90 s	16.55 s	[+1.0%; +3.3%] (maybe worse)
startup:petclinic:iast:Agent	16.88 s	16.42 s	[-1.8%; +7.5%] (no difference)
startup:petclinic:profiling:Agent	16.90 s	16.91 s	[-1.3%; +1.1%] (no difference)
startup:petclinic:sca:Agent	16.98 s	16.86 s	[-0.2%; +1.6%] (no difference)
startup:petclinic:tracing:Agent	16.11 s	16.10 s	[-0.7%; +0.8%] (no difference)

Commit: 3a33bcd4 · 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.

[dd-octo-sts]

Hi! 👋 Thanks for your pull request! 🎉

To help us review it, please make sure to:

• Add at least one type, and one component or instrumentation label to the pull request

If you need help, please check our contributing guidelines.

[datadog-prod-us1-5]

More details

The bump is internally consistent: both the version catalog and ddprof-lib lockfile now select ddprof 1.48.0, and no other stale ddprof 1.47.0 references remain. Profiling tests could not start because this sandbox lacks the repository's required Java 25 toolchain, so binary compatibility was not executed locally.

Was this helpful? React 👍 or 👎

_{Open Bits AI session}

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

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-07-28 11:52:40 UTC ℹ️ Start processing command /merge

---

2026-07-28 11:52:45 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-07-28 12:51:20 UTC ❌ MergeQueue: The build pipeline contains failing jobs for this merge request

Build pipeline has failing jobs for b0f8581:

• test_ssi_smoke: [8, 2/8]

⚠️ Do NOT retry failed jobs directly (why?).

What to do next?

• Investigate the failures and when ready, re-add your pull request to the queue!
• If your PR checks are green, try to rebase/merge. It might be because the CI run is a bit old.
• Any question, go check the FAQ.

Details

Since those jobs are not marked as being allowed to fail, the pipeline will most likely fail.
Therefore, and to allow other builds to be processed, this merge request has been rejected and the pipeline got canceled.

[kaahos]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-07-28 13:22:02 UTC ℹ️ Start processing command /merge

---

2026-07-28 13:22:07 UTC ℹ️ MergeQueue: pull request added to the queue

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

---

2026-07-28 14:26:34 UTC ℹ️ MergeQueue: This merge request was merged

[bric3]

Thanks for the changelog :)