Desktop app: infinite React render loop causes OOM crash, kills Chrome

Description

The Claude desktop app (Windows, v1.8555.2.0) hits an infinite React render loop that eventually causes an out-of-memory crash. The crash cascades to kill Google Chrome (shared Chromium GPU process), and orphaned child processes prevent the app from restarting ("program being used in the background").

Steps to reproduce

Occurred during normal usage on Windows 11 Pro (10.0.26200). Exact trigger unclear — happened during a Claude Code session on June 1, 2026 around 7:17 PM PT.

Log evidence (from %APPDATA%\Claude\logs\)

unknown-window.log:

2026-06-01 19:17:54 [error] Maximum update depth exceeded. This can happen when a component calls setState inside useEffect, but useEffect either doesn't have a dependency array, or one of the dependencies changes on every render.
2026-06-01 19:27:13 [error] Maximum update depth exceeded. [same]
2026-06-01 19:28:12 [error] Uncaught DataCloneError: Failed to execute 'measure' on 'Performance': Data cannot be cloned, out of memory.
2026-06-01 19:28:12 [error] Uncaught Error: Should not already be working.
2026-06-01 19:28:12 [error] Uncaught Error: Should not already be working.

main1.log:

2026-06-01 19:31:28 [error] Sentry caught: {
  eventId: 'cc130bdd555942c0983380dc0f2e180e',
  type: 'Unknown',
  value: 'No message',
  stack: undefined
}

Impact

1. Claude app crashes (OOM from infinite useEffect render loop)
2. Chrome killed (shared Chromium GPU process cascade)
3. App won't reopen — orphaned claude.exe and node.exe child processes hold the single-instance lock

Environment

• Windows 11 Pro 10.0.26200
• Claude Desktop v1.8555.2.0 (Windows Store / MSIX)
• Sentry event ID: cc130bdd555942c0983380dc0f2e180e