Three components reproducibly time out and take the bridge connection with them.
Render failed: Error: Timed out waiting for renderComponent-result.
Immediately afterwards http://localhost:9002/status reports {"connections":[]} — the plugin is gone.
Evidence
Three separate attempts each, across three runs, same result every time. This is not the incidental disconnect caused by a plugin rebuild mid-run; nothing was rebuilding during the last two attempts.
Two observations that narrow it:
Toast has a single variant, so raw size is not the explanationText rendered and round-tripped successfully earlier the same day, when the target page held far fewer components
Fixtures
Text — 54 variantsTextInput — 31 variantsToast — 1 variant
The Toast case is the most valuable: whatever the cause is, it is not variant volume.
Where
Undetermined. The artifacts cannot distinguish a plugin worker crash from a render that never terminates. The plugin console during a render attempt is the first place to look, since the CLI-side timeout gives no detail.
Verification
Each of the three renders to completion, and the bridge still reports a connected plugin afterwards.
Note
Render onto a dedicated page with an explicit --page. These renders use --overwrite, which deletes the existing same-titled component before rendering — a timeout can therefore leave the component deleted and not replaced.
Part of #281.
Three components reproducibly time out and take the bridge connection with them.
Immediately afterwards
http://localhost:9002/statusreports{"connections":[]}— the plugin is gone.Evidence
Three separate attempts each, across three runs, same result every time. This is not the incidental disconnect caused by a plugin rebuild mid-run; nothing was rebuilding during the last two attempts.
Two observations that narrow it:
Toasthas a single variant, so raw size is not the explanationTextrendered and round-tripped successfully earlier the same day, when the target page held far fewer componentsFixtures
Text— 54 variantsTextInput— 31 variantsToast— 1 variantThe
Toastcase is the most valuable: whatever the cause is, it is not variant volume.Where
Undetermined. The artifacts cannot distinguish a plugin worker crash from a render that never terminates. The plugin console during a render attempt is the first place to look, since the CLI-side timeout gives no detail.
Verification
Each of the three renders to completion, and the bridge still reports a connected plugin afterwards.
Note
Render onto a dedicated page with an explicit
--page. These renders use--overwrite, which deletes the existing same-titled component before rendering — a timeout can therefore leave the component deleted and not replaced.Part of #281.