test(browser): measure bounded Chromium process-tree RSS

[seonghobae]

Partial implementation of #28, stacked on exact current PR #72 head e0b5d43c3a869605aaefa2e4752de7b1b641ddbd.

Buyer-visible gap

PR #72 measures the ChromeDriver-reported browser root PID, observation bytes, action latency and task duration, but a single root PID materially undercounts Chromium renderer/GPU/utility descendants. This lane adds one bounded sampled Linux process-tree RSS evidence path for the controlled Agent Task.

Dependency / current stack

Current exact #73 head is 6ba2d03345fa3153230a7d365fba8284696541a1. Fresh compare against exact current #72 head e0b5d43c3a869605aaefa2e4752de7b1b641ddbd reports behind_by=0 with merge base exactly equal to that prerequisite. Keep Draft while #72/#71/#70/#65 remain active. No prerequisite result transfers.

TDD / RCA lineage

Earlier test-first work established bounded /proc process-tree discovery, one sampled PID/PPID/RSS snapshot, strict process identity parsing, bounded process-set aggregation, and chromium_process_count / chromium_process_set_rss_bytes evidence.

Two concrete defects were then corrected rather than normalized away:

• a sampled descendant with no resident VmRSS remains part of process-tree membership/count but contributes no resident bytes; malformed membership and aggregate overflow remain fail closed; and
• optional/nonresident VmRSS is distinguished from malformed/ambiguous status input, so duplicate, malformed-unit, malformed-shape/value and overflow evidence is rejected rather than converted to absence.

The current branch has also been non-destructively aligned to the exact current #72 prerequisite. The implementation tree remains the bounded process-snapshot evidence lane; no prerequisite check/review is reused.

Exact-head proof

On unchanged exact head 6ba2d03345fa3153230a7d365fba8284696541a1 against exact current #72 head e0b5d43c3a869605aaefa2e4752de7b1b641ddbd:

• CI run 31550050786: success, including repository contracts, canonical formatting, locked workspace/all-target check, full tests, strict Clippy, rustdoc and exact owned production function/line/region/branch coverage;
• Manifest V3 Compatibility run 31550050775: success on the same exact head;
• fresh ancestry comparison reports test(browser): measure bounded Chromium process-tree RSS #73 ahead of test(browser): record controlled Agent Task resource evidence #72 with no dependency lag; and
• no inline review threads are currently returned.

No predecessor-head result is transferred.

Truth boundary

This remains controlled Linux CI evidence, not trusted product process-attribution authority. It sums resident RSS only for processes present in one bounded /proc lineage snapshot rooted at the ChromeDriver-issued browser PID. It does not prove per-tab/task ownership, cgroup ownership, CPU, GPU/VRAM, JS heap, cross-platform semantics, or compose a trusted production browser/process adapter. No whole-task RSS claim is permitted until that attribution boundary exists.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: fa7c919d-6c2c-4b5e-83ed-396c507f6baa

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}