| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Scan-Build Report
Bug Summary
Reports
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Sorry, something went wrong.
CI Test ResultsRun: #37616728506 | Commit: e9e835c | Duration: 17m 28s (longest job)
Status Overview
Legend: ✅ passed | ❌ failed | ⚪ skipped | 🚫 cancelled Summary: Total: 32 | Passed: 32 | Failed: 0 Updated: 2026-10-07 12:10:47 UTC |
Sorry, something went wrong.
Sorry, something went wrong.
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Sorry, something went wrong.
There was a problem hiding this comment.
Here are some automated review suggestions for this pull request.
Reviewed commit: 93f2dbf486
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
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".
Sorry, something went wrong.
There was a problem hiding this comment.
Stopping a recording can omit all reference-chain events since the last dump. The lifecycle also keeps strong thread references and stale chain data across recording sessions.
🤖 Datadog Autotest · Commit 93f2dbf · What is Autotest? · @DataDog review to ask questions · Any feedback? Reach out in #autotest
Sorry, something went wrong.
Introduces the ReferenceChainEvent/ReferenceChainAbandonedEvent payloads (event.h), their JFR metadata (jfrMetadata.*), and the FlightRecorder emission paths that serialize chain events into JFR recording buffers, including the constant-pool handling for per-hop edge labels. Emission is pull-style: profiler.cpp snapshots events and hands them to FlightRecorder; this layer does not depend on the tracker itself.
- ReferenceChainEvent carries one vector of ReferenceChainHop (klass id + retention-edge label) instead of two parallel vectors - Compress the sub-option floor/ceiling rationale and the provisional default constant comments to one concise statement each - Drop design-doc and Jira references from code comments; revert the unrelated LineNumberTable comment rewrite
- cleanup_table: account_epoch flag; track() overflow sweep skips epoch claim - admitForTracking: LIVENESS_URGENT_BOOST_ADMITS/BACKED_OFF counters - secondsToOOM: zero-denominator guard; ringThirdsStats -> ringWindowStats - JNI poll seam calls finishLoopIterationSerialized - gtests: DipThenRecover, OddLengthRisingWindow
…rences pause - heapReferenceCallback ran invalidateResolvedChain() inside the FollowReferences STW pause, taking _resolved_chains_lock, which drainPendingChainEvents() holds across its cache copy on the JFR dump thread. Evictions are now queued and applied on the BFS thread outside any walk. - PriorityExpandSet::insert() had no occupancy bound and could spin forever on a full table; it now returns false.
… seam - referenceChainsPesTests.inc: PriorityExpandSet round-trip, rebuildFrom, full-table self-termination; ClassTagAllocator negative-tag minting - referenceChainsTestAccessors.h: cacheChain() passes source_tag and source_tag_val through unchanged - referenceChainsOomTests.inc: setCanaryBackoffForTest() takes ns
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
Here are some automated review suggestions for this pull request.
Reviewed commit: d21eb089f7
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
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".
Sorry, something went wrong.
There was a problem hiding this comment.
Sorry, something went wrong.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
There was a problem hiding this comment.
Sorry, something went wrong.
|
Fixed in 0668fa1 (addressing general review comment). |
Sorry, something went wrong.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
Sorry, something went wrong.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
| Back | FazBrowse Home | New Git URL |
What does this PR do?:
Hooks the reference-chain engine into the profiler lifecycle. Profiler starts and stops ReferenceChainTracker and LivenessTracker together with the recording, writes resolved chains into JFR on dump() and emits abandoned-search events. vmEntry GC hooks feed the tracker, and there are new JFR event types for the chains.
ObjectSampler now always passes the recording's flags to LivenessTracker, so they can't go stale between recordings. LivenessTracker is started last; if it fails to start, the sampler is deactivated and SAMPLED_OBJECT_ALLOC is disabled again.
javaApi.cpp adds the reference-chain natives and test seams, declared in JavaProfiler.java. The seams are real only in debug builds - release builds export no-op stubs, so calling them never throws UnsatisfiedLinkError.
Motivation:
Makes the reference-chain tracker reachable from a live recording.
Additional Notes:
A few engine fixes ride along:
How to test the change?:
For Datadog employees:
credentials of any kind, I've requested a security review (run the dd:platform-security-review
skill, or file a request via the PSEC review form).
bewaire also runs automatically on every PR.
🤖 Generated with Claude Code