Skip to content

[bug] White Screen of Death #4904

Open
Open

Description

@TrapperBo

What happened

Had a force close twice in this prompt. Both using Rive. Screen went white and no longer responded.

Screenshot

Screenshot status: declined

Chat session

Session ID: v2:9f80da62-2b24-47b9-b37e-8144e61ed40b
Session Schema: v2.0

System Information

  • Dyad Version: 1.21.0-beta.2
  • Platform: win32
  • Architecture: x64
  • Node Version: v24.18.0
  • PNPM Version: 11.28.2
  • Node Path: C:\Users\beaug\AppData\Roaming\dyad\managed-tools\node\v24.18.0\node.exe
    C:\Program Files
  • Pro User ID: ****iLCm
  • Telemetry ID: b05f6e4b-e2b6-44d2-aaa1-151815ce1fcb
  • Model: claude-code:claude-opus-5-5 | customId: undefined

Settings

  • Selected Model: claude-code:claude-opus-5-5
  • Chat Mode: local-agent
  • Auto Approve Changes: n/a
  • Dyad Pro Enabled: true
  • Effort Level: medium
  • Runtime Mode: host
  • Release Channel: beta

Logs

    at JW (C:\Users\beaug\AppData\Local\dyad\app-1.21.0-beta2\resources\app.asar\.vite\build\main-9T3GTVPV.js:4416:26526)
    at async XU (C:\Users\beaug\AppData\Local\dyad\app-1.21.0-beta2\resources\app.asar\.vite\build\main-9T3GTVPV.js:4416:23415)
  source: 'remote',
  version: '2026-10-24T00:05:42.190Z',
  expiresAt: '2026-10-24T01:05:42.190Z'
}
  source: 'remote',
  version: '2026-10-24T00:05:42.190Z',
  providerCount: 5
}
  source: 'remote',
  version: '2026-10-24T00:05:42.190Z',
  expiresAt: '2026-10-24T01:05:42.190Z'
}
  source: 'remote',
  version: '2026-10-24T00:05:42.190Z',
  providerCount: 5
}
C:\Program Files\nodejs\node.exe

Auto-Updater Logs

sImpl: Starting fixPinnedExecutables
[22/10/26 14:05:54] info: ApplyReleasesImpl: Fixing up tray icons
[22/10/26 14:05:54] info: ApplyReleasesImpl: cleanDeadVersions: checking for version 1.21.0-beta2
[22/10/26 14:05:54] info: ApplyReleasesImpl: cleanDeadVersions: exclude current version folder app-1.21.0-beta1
[22/10/26 14:05:54] info: ApplyReleasesImpl: cleanDeadVersions: exclude new version folder app-1.21.0-beta2
[22/10/26 14:05:55] info: Program: Finished Squirrel Updater

Activity

  1. added
    bugSomething isn't working
    probugs filed from pro members
    triage/needs-humanThe triage bot could not help with this issue; a person needs to reply
    on Oct 24, 2026
  2. dyad-assistant commented on Oct 24, 2026

    @dyad-assistant
    Contributor

    Hi @TrapperBo, thanks for sending this from Dyad.

    What's going on: Dyad went white and stopped responding twice while working with your Rive plugin in this chat. We can't tell the cause from the logs in this report, but your chat session gives the team enough to look into it.

    What you can do now: If it happens again, open Help > Report a Bug with Chat session turned on right after you reopen Dyad, so the team gets the logs from the crash.

    Someone from the Dyad team will follow up here.

    Notes for the Dyad team
    • 1.21.0-beta.2 (current), win32 x64, claude-code:claude-opus-5-5, local-agent mode, Pro, beta channel, effort medium.
    • Symptom: renderer goes white and unresponsive (force close x2) while using the Rive MCP plugin (custom http MCP server from [bug] Plugin Issue #4885/[bug] Plugin Issue #4885 Bug Report From Dyad #4886, same reporter).
    • Logs are trimmed: only a minified stack tail (JW / async XU in main bundle) and remote provider-config lines; no error message survives. Auto-Updater section is the normal Squirrel apply (beta1 -> beta2), unrelated.
    • Hypothesis (unverified): large MCP tool results from Rive (e.g. binary/animation payloads) bloating the chat render or renderer memory. Pull session v2:9f80da62-... for the full main log.
    • Evidence for needs_human: playbook crash-force-close; no readable cause in logs.
    • Confidence: low on cause.
    • Assessment: needs_human · Playbook: crash-force-close
    • Possibly related: [bug] Plugin Issue #4885 (same reporter; Rive MCP plugin 'Tool discovery failed', closed completed — crash may involve the same Rive MCP server once connected), Dyad suddenly started to generate a big blank / white screen #1802 (older white-screen-during-prompt report, closed after perf work), HIGH MEMORY CONSUMPTION #3235 (white screen with high renderer memory use)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingprobugs filed from pro memberstriage/needs-humanThe triage bot could not help with this issue; a person needs to reply

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions