Opening Cloudflare dashboard in Browser pane crashes GPU process (exitCode 101457950), app becomes unlaunchable and requires OS repair
Description
Opening the Cloudflare dashboard (https://dash.cloudflare.com) in the Browser pane reliably crashes the GPU process, which brings down the whole Claude Desktop app. After the crash, the app could not be relaunched normally — a full Windows repair was required to recover it.
Reproducibility note: In my testing, this was 100% reproducible (2/2) specifically when opening the Cloudflare dashboard in the Browser pane. I want to be precise about scope: simply opening the Browser pane and taking a screenshot does not appear to be sufficient on its own to trigger the crash — see "What I ruled out" below. It's possible other sites with similarly heavy/complex rendering could trigger the same underlying issue, but I haven't confirmed that; Cloudflare's dashboard is the only page I've confirmed it against.
Environment
- Claude Desktop version:
1.34493.1(installed via Microsoft Store / MSIX) - CCD version:
2.1.237 - Claude Code CLI version:
2.1.227 - OS: Windows 11 Home, build 10.0.26200, x64
- Node:
24.18.1
Steps to reproduce
- In a Claude Code session, open the Browser pane on
https://dash.cloudflare.com(e.g. viapreview_startwith thaturl). - Within ~9 seconds, the GPU process crashes on its own (before any explicit screenshot action was even issued in one of the two occurrences).
- The app window disappears shortly after.
Reproduced 2/2 times, both times ~9 seconds after the Cloudflare dashboard preview tab was opened, with an identical exit code.
Actual behavior
main.log shows the same sequence both times:
[warn] [Preview] capturePreviewScreenshotIfChanged failed: {
error: [Error: UnknownVizError] {
[stack]: [Getter/Setter],
[message]: 'UnknownVizError'
}
}
[info] GPU process gone: {
type: 'GPU',
reason: 'crashed',
exitCode: 101457950,
serviceName: 'GPU'
}
(Order of the two log lines swapped slightly between the two occurrences, but the exitCode was identical both times: 101457950.)
Timestamps confirm the ~9s window both times:
- Occurrence 1: preview tab opened at 21:04:23, GPU crash at 21:04:32
- Occurrence 2: preview tab opened at 21:13:43, GPU crash at 21:13:52
After the second crash, the app would not start again at all — not just this session, but the app itself. A full Windows repair was required before Claude Desktop could launch again. This is the most concerning part: a GPU child-process crash appears to have left the app (or its local state) corrupted enough to block startup entirely.
What I ruled out
The same internal warning (capturePreviewScreenshotIfChanged failed: UnknownVizError) also appeared once earlier in the same session (20:56:36) while previewing a local static file server (a plain local HTML page, not an external site) — and that occurrence did not crash the GPU process; the app continued running normally for several more minutes afterward. So the UnknownVizError warning alone isn't sufficient to reproduce the crash; both actual crashes specifically involved the Cloudflare dashboard page.
Expected behavior
- A GPU process crash should not take down the whole app, and should definitely not corrupt local state badly enough to require an OS-level repair to recover.
- At minimum, the preview screenshot capture (
capturePreviewScreenshotIfChanged) should degrade gracefully onUnknownVizErrorinstead of taking the GPU process down with it.
Additional notes
- Crash dumps:
Crashpad\reportswas empty in%APPDATA%\Claude\Crashpadfor both incidents — the crash reporter doesn't appear to have captured a report for this failure mode, which may be worth looking into separately. - Happy to provide more of
%LOCALAPPDATA%\Claude\Logs\main.logaround the incident timestamps if useful (redacted the parts referencing local project paths / account identifiers before writing this report).
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗