Repository navigation
Deliver an initial browser frame to overlapping static-page watchers - #63
Draft
Fectivnfy112357 wants to merge 1 commit into
Draft
Fectivnfy112357 wants to merge 1 commit into
Fectivnfy112357 wants to merge 1 commit into
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proven: a late watcher can starve on a static Chromium page
On the current main runtime, an active watcher receives the page's only JPEG. A second watcher of the same target joins the existing cast, but it receives nothing until the page paints again. A gated fake provider reproduces this. A real local Chromium control saw the same starvation both at 600×500 and after a genuine resize to 700×550; evaluating the live viewport confirmed that the resize took effect without producing a frame.
Provide a fresh one-shot initial image only for an overlapping subscriber that still has no live frame. The original screencast remains active; a live frame wins, errors retain the existing live and timeout behavior, and the image is not broadcast or cached. The capture stays on the authorized Chromium target and checks generation, stream ownership and confident viewport geometry again before delivering. Concurrent resize writes with uncertain ordering skip the supplemental capture. At most one supplemental native capture is in flight per page.
CI attribution
Main run 209 macOS recorded one JPEG for an earlier watch, then a later watch with no image and no error. This is consistent with the reproduced defect, but that run did not record the overlap or viewport at the service, so it does not prove this exact cause. No timeouts or assertions weakened.
Verification