Bump ddprof to 1.46.0

[jbachorik]

What Does This Do

Bump Java profiler to bring in latest fixes

Motivation

Additional Notes

Noticeable fixes

• An alternative TLS implementation to fix a crash on musl/aarch64 by @zhengyu123 in An alternative TLS implementation to fix a crash on musl/aarch64 java-profiler#600
• Don't preload jmethodIDs when cstack=vm with hotspot JVM by @zhengyu123 in Don't preload jmethodIDs when cstack=vm with hotspot JVM java-profiler#549
• fix(context): scope OTEL ThreadContext storage to the carrier thread (PROF-15271) by @rkennke in fix(context): scope OTEL ThreadContext storage to the carrier thread (PROF-15271) java-profiler#625
• fix(profiler): close two TOCTOU races between SIGPROF handler and JFR lifecycle by @r1viollet in [PROF-15201] fix(profiler): close two TOCTOU races between SIGPROF handler and JFR lifecycle java-profiler#614

See full release 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
• Add your completed PR to the merge queue by commenting /merge. You can also:
  • Customize the commit message associated with the merge with /merge --commit-message "..."
  • Remove your PR from the merge queue with /merge -c
  • Skip all merge queue checks with /merge -f --reason "reason"; please use this judiciously, as some checks do not run at the PR-level (note: the PR still needs to be mergeable, this will only skip the pre-merge build)
  • Get more information in this doc

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8a8231aff1

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that 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.90 s	14.65 s	[+0.8%; +2.5%] (maybe worse)
startup:insecure-bank:tracing:Agent	13.63 s	13.70 s	[-1.3%; +0.3%] (no difference)
startup:petclinic:appsec:Agent	16.75 s	16.76 s	[-1.0%; +0.9%] (no difference)
startup:petclinic:iast:Agent	16.91 s	16.56 s	[-2.5%; +6.8%] (no difference)
startup:petclinic:profiling:Agent	16.81 s	16.95 s	[-2.1%; +0.5%] (no difference)
startup:petclinic:sca:Agent	16.86 s	16.70 s	[+0.2%; +1.7%] (maybe worse)
startup:petclinic:tracing:Agent	16.11 s	15.86 s	[+0.3%; +2.8%] (maybe worse)

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

[jbachorik]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-07-05 11:11:48 UTC ℹ️ Start processing command /merge

---

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

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

---

2026-07-05 13:12:13 UTC ❌ MergeQueue: The build pipeline has timeout

The merge request has been interrupted because the build 2150195567603788605 took longer than expected. The current limit for the base branch 'master' is 120 minutes.

Possible reasons:

• some mandatory checkruns are failing:
  • Check pull request labels
  • Check pull requests
  • Enforce Groovy migration

[bric3]

Ideally a small change log would be nice.