Session failed: React Render Loop crashes SessionUI repeatedly (Windows ARM64, exit code 3)

Bug Description

Claude Code sessions crash repeatedly with "Session failed" error. The Claude Code process exits with code 3, triggered by a React render loop in the SessionUI component. Sessions become unusable after a few minutes of work.

Environment

• Claude Desktop: 1.1.3963 (MS Store, Windows)
• Claude Code: 2.1.50 (also occurred on 2.1.49)
• Platform: Windows 11 ARM64 (10.0.26200)
• CPU: Snapdragon X 12-core X1E80100 @ 3.40 GHz
• RAM: 16 GB
• Entrypoint: claude-desktop

Steps to Reproduce

1. Open Claude Desktop on Windows ARM64
2. Start a Claude Code session (any project)
3. Work normally (tool calls, file reads, etc.)
4. After a few minutes → "Session failed"
5. Resuming crashes again within minutes

Error Logs

Primary: React Render Loop (claude.ai-web.log)

[LOCAL_SESSION] [RenderLoopDetector] RENDER LOOP in SessionUI: 
40 renders in 1000ms. React will crash with error #185 
(Maximum update depth exceeded). Diagnostics: {}

Secondary: Process Crash (main.log)

Session local_431f490b query error: Claude Code process exited with code 3
error_category: 'process_crashed'

Sentry Error

Sentry caught: {
  type: 'Error',
  value: 'ProcessTransport is not ready for writing'
}

Session Directory Missing

ENOENT: no such file or directory, scandir '...\claude-code-sessions\...'
[LocalSessionManager] loadSessions failed during account transition

Crash Timeline (2026-02-23, single session)

| Time | Event |
|------|-------|
| 00:15 | Render loop |
| 00:23 | Process crash (exit 3) |
| 00:25 | Process crash (exit 3) |
| 00:28 | Process crash (exit 3) |
| 00:31 | Process crash (exit 3) |
| 00:34 | Process crash (exit 3) |
| 00:36 | Process crash (exit 3) |
| 00:41 | Sentry: "ProcessTransport is not ready for writing" |
| 00:42 | Process crash (exit 3, startup_error + resume) |
| 00:45 | Process crash (exit 3) |
| 01:02 | Render loop |

Notes

• IdleManager continuously warms up crashed session → crash loop
• is_startup_error: true + is_resume: true → sessions crash immediately on resume
• Diagnostics: {} is empty → no state info available for debugging
• AxiosErrors also appear in ~/.claude/debug/ logs