[GH-ISSUE #557] browser: cancellation-blind teardown and over-eager WebMCP frame pruning #283

New issue

Closed

opened 2026-10-15 18:23:27 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 18:23:27 +00:00

Owner

Originally created by @morluto on GitHub (Oct 5, 2026).
Original GitHub issue: https://github.com/morluto/rea/issues/557

Remaining scope

Live findings remain cancellation-blind V8/Playwright close paths and WebMCP subtree pruning on transient frame navigation. Reuse lifecycle ownership/cancellation behavior, avoid a hung peer blocking completion, and distinguish genuine scope exit from about:blank or intermediate reload state. Frame loss should not permanently claim tools are absent. Verify both transport seams and the matching real-browser lane.

Verification

Exercise representative valid and malformed producer data through the consumer boundary and assert the resulting observations, unknowns, or actionable failure. Keep CLI/MCP behavior aligned where applicable.

This scope was refreshed after removal of replay and permission plumbing and merge of PR #538; implementation is being addressed in the boundary root-cause cleanup.

Originally created by @morluto on GitHub (Oct 5, 2026). Original GitHub issue: https://github.com/morluto/rea/issues/557 ## Remaining scope Live findings remain cancellation-blind V8/Playwright close paths and WebMCP subtree pruning on transient frame navigation. Reuse lifecycle ownership/cancellation behavior, avoid a hung peer blocking completion, and distinguish genuine scope exit from about:blank or intermediate reload state. Frame loss should not permanently claim tools are absent. Verify both transport seams and the matching real-browser lane. ## Verification Exercise representative valid and malformed producer data through the consumer boundary and assert the resulting observations, unknowns, or actionable failure. Keep CLI/MCP behavior aligned where applicable. This scope was refreshed after removal of replay and permission plumbing and merge of PR #538; implementation is being addressed in the boundary root-cause cleanup.

bsakaguchi

2026-10-15 18:23:27 +00:00