Bump ddprof to 1.46.0

[jbachorik]

What Does This Do

Bump Java profiler to bring in latest fixes

Motivation

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
• 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".

[chatgpt-codex-connector]

Regenerate the ddprof dependency lock

Because dependency locking is enabled via lockAllConfigurations() and dd-java-agent/ddprof-lib/gradle.lockfile still pins com.datadoghq:ddprof:1.45.0, normal builds of :dd-java-agent:ddprof-lib will keep using the locked 1.45.0 artifact instead of the catalog's new 1.46.0 version. Please update/regenerate that lockfile along with this bump so the agent actually ships the intended profiler fixes.

Useful? React with 👍 / 👎.

[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.01 s	13.94 s	[-0.4%; +1.4%] (no difference)
startup:insecure-bank:tracing:Agent	12.91 s	12.99 s	[-1.5%; +0.2%] (no difference)
startup:petclinic:appsec:Agent	16.89 s	16.70 s	[+0.0%; +2.2%] (maybe worse)
startup:petclinic:iast:Agent	16.91 s	16.95 s	[-1.0%; +0.5%] (no difference)
startup:petclinic:profiling:Agent	16.62 s	16.92 s	[-2.8%; -0.8%] (maybe better)
startup:petclinic:sca:Agent	16.21 s	16.84 s	[-8.1%; +0.6%] (no difference)
startup:petclinic:tracing:Agent	16.14 s	15.98 s	[+0.1%; +2.0%] (maybe worse)

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