SSR_LIVE_HOLE_LATCHED
A live hole that shipped its markers was closed by the impurity gate on re-run and stopped updating (dev).
What you saw
- Kind:
ssr - Severity:
warn(code that works but is structurally wrong or expensive)
The console report opens with [SSR_LIVE_HOLE_LATCHED] and the message, then an in line naming the owners that enclose the subject, root first, and an at line with the source location when the code was compiled with one.
In a captured artifact the same finding is an event with code: "SSR_LIVE_HOLE_LATCHED", ownerPath, and loc.
Diagnostics explains each line.
Why it fires
A live markup hole (or attribute) in a server component shipped its markers and then stopped updating: re-running it created a reactive scope still waiting on async work (data.cause: "owners") or emitted slot records ("records"), so the runtime closed it and the client keeps the markup it last received.
Scopes that finish synchronously (a nested <For>, a condition memo such as {m.usage && …}, a component) are fine: each re-run gets a throwaway scope.
The usual cause is a memo over a fetch or a stream created inside the markup that re-renders, which would restart on every re-run.
The server runtime reports on the same channel, with the same in <App> › <Page> line.
Two groups.
Findings (SSR_RENDER_ERROR_CONTAINED, SSR_SUBTREE_ABANDONED, SSR_STREAM_ABANDONED, LATE_HEADER_WRITE, DYNAMIC_ASYNC_COMPONENT, SERVER_ERROR_SANITIZED, FRAME_MARKER_CORRUPTED) are facts about a render that exist in observe builds too — an APM sees them in production; in dev they print.
Checks (the rest, SSR_BOUNDARY_WATERFALL and SSR_CLIENT_CONTENT_MASKED included) are dev-only guidance.
A captured artifact from a server render carries both.
How to fix it
Create the async source in the component body instead. The finding is located by the component the hole is in.
In tests
captureArtifact from @solidjs/diagnostics runs a scenario with the diagnostics channel open and returns the events it saw.
expectNoDiagnostics(artifact) fails while SSR_LIVE_HOLE_LATCHED is among them, with the events as evidence; after the fix, the code is gone from artifact.diagnostics.
Check for regressions in tests shows the loop and the Vitest matcher form.
Learn more
- Diagnostics: every code, with its kind, severity, and trigger.
- Debugging reactivity: how to read a report and what each group of codes points at.