FRAME_MARKER_CORRUPTED
Frame slot range missing its end marker on the client — nesting or an HTML rewriter (observe + dev).
What you saw
- Kind:
ssr - Severity:
error(broken behavior)
The console report opens with [FRAME_MARKER_CORRUPTED] 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: "FRAME_MARKER_CORRUPTED", ownerPath, and loc.
Diagnostics explains each line.
Why it fires
(Client.) A frame's slot start marker has no end marker among its siblings: invalid HTML nesting split the range when the browser parsed it (a block element inside <p>, a <tr> outside a table), or a CDN/minifier stripped the comment.
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
Fix the nesting in the server component's markup; serve frame documents with Cache-Control: no-transform.
In tests
captureArtifact from @solidjs/diagnostics runs a scenario with the diagnostics channel open and returns the events it saw.
expectNoDiagnostics(artifact) fails while FRAME_MARKER_CORRUPTED 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.