Recurring Bun crash on Windows: panic(main thread): switch on corrupt value

Resolved 💬 4 comments Opened Feb 18, 2026 by Infinitegameworks Closed Mar 2, 2026

Environment

  • Claude Code version: 2.1.45
  • Bun: Canary v1.3.10-canary.63 (1979c945)
  • OS: Windows 11 Pro 10.0.26100 (win11_dt)
  • CPU: x64 (baseline) — sse42 avx avx2
  • Machine RAM: 16.44GB

Crash Details

panic(main thread): switch on corrupt value

RSS: 0.62GB | Peak: 0.67GB | Commit: 0.92GB | Faults: 232217
Elapsed: 29596ms | User: 4343ms | Sys: 1203ms
Features: Bun.stderr(2) Bun.stdin(2) Bun.stdout(2) fetch(29) jsc spawn(16) standalone_executable process_dlopen yaml_parse(88)

Bun crash report link: https://bun.report/1.3.10/e_21979c94mgkgEugogC09gkQ4p4vbq705Vwws1U23wN284hUm5nlOiq4kOwkzjwDCYKERNEL32.DLLut0LCSntdll.dll4gijBA0eNorLs8sSc5QyM9TSM4vKiotKFEoS8wpTQUAa8EI/A

Behavior

  • Crash occurs randomly — no consistent trigger identified
  • Has happened multiple times across different sessions
  • No specific operation (multi-agent, file reads, etc.) consistently reproduces it
  • The switch on corrupt value panic suggests a GC race or memory corruption in Bun's JSC backend on Windows

Expected Behavior

Claude Code should not crash with a Bun runtime panic during normal usage.

Additional Context

Installed via npm (@anthropic-ai/claude-code). Running as standalone executable at C:\Users\bluey\.local\bin\claude.exe.

View original on GitHub ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗