Context
This is mode B of the quarantined Workstation film tour (5 arms, 4 of them the viewer-driven arm; same runs as mode A). It fails with journey hop 4 (target): the target did not take the drag…: claim, preview and indicators all agree, but the cross-window proxy reads settled:false. The viewer arm's quarantine reason ("stops at journey hop 3") is therefore mostly wrong.
The Problem (inferred, ~45 %)
App#insertThemeFiles decrements countLoadingThemeFiles only in .then (src/worker/App.mjs ~484–492). A reply from a window that has departed either rejects (src/worker/Base.mjs ~527) or never arrives, so the counter can stay above zero. The counter is shared across the whole App worker and parks every initVnode(true) and updateVdom (src/mixin/VdomLifecycle.mjs ~766, ~1362). The header proxy mounts that way (src/dashboard/dock/window/VesselProxyEmbodiment.mjs ~274–287), and the snapshot's ready requires settled (apps/workstation/view/CrossWindowGestureSnapshot.mjs ~121). The journey's short-lived vessels (see the mode-A ticket) supply the departing windows.
The Fix
- First, confirm: put
countLoadingThemeFiles in the hop-4 diag. A 0 there falsifies this cause.
- Decrement in
finally, and preferably count per window, so one departed window cannot park another's updates.
Acceptance Criteria
Related
Parent #19655 · the mode-A ticket filed alongside this one.
Sweeps at 11:00Z: live latest-20 open issues, A2A claims (none).
Origin Session ID: 1cc54e4a-b230-43bc-ac83-7519d425f6e7
Context
This is mode B of the quarantined Workstation film tour (5 arms, 4 of them the viewer-driven arm; same runs as mode A). It fails with
journey hop 4 (target): the target did not take the drag…: claim, preview and indicators all agree, but the cross-window proxy readssettled:false. The viewer arm's quarantine reason ("stops at journey hop 3") is therefore mostly wrong.The Problem (inferred, ~45 %)
App#insertThemeFilesdecrementscountLoadingThemeFilesonly in.then(src/worker/App.mjs~484–492). A reply from a window that has departed either rejects (src/worker/Base.mjs~527) or never arrives, so the counter can stay above zero. The counter is shared across the whole App worker and parks everyinitVnode(true)andupdateVdom(src/mixin/VdomLifecycle.mjs~766, ~1362). The header proxy mounts that way (src/dashboard/dock/window/VesselProxyEmbodiment.mjs~274–287), and the snapshot'sreadyrequiressettled(apps/workstation/view/CrossWindowGestureSnapshot.mjs~121). The journey's short-lived vessels (see the mode-A ticket) supply the departing windows.The Fix
countLoadingThemeFilesin the hop-4 diag. A 0 there falsifies this cause.finally, and preferably count per window, so one departed window cannot park another's updates.Acceptance Criteria
updateVdom; red before and green after.binder=null themeFileLoads=0, a third cause, and timed out its shard; the film arms stay quarantined until #19919 lands.Related
Parent #19655 · the mode-A ticket filed alongside this one.
Sweeps at 11:00Z: live latest-20 open issues, A2A claims (none).
Origin Session ID: 1cc54e4a-b230-43bc-ac83-7519d425f6e7