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

Resolved 💬 9 comments Opened Feb 19, 2026 by jiaoshi888 Closed Mar 2, 2026

Bug Description

Claude Code crashes with a Bun runtime panic after extended usage on Windows 10.

Error Message

panic(main thread): switch on corrupt value
oh no: Bun has crashed. This indicates a bug in Bun, not your code.

Environment

  • OS: Windows 10 x64 (win10_ni)
  • Bun version: v1.3.10 (1423d3c8)
  • CPU: sse4.2 avx avx2
  • Claude Code path: C:\Users\Administrator\.local\bin\claude.exe

Runtime Stats at Crash

  • Elapsed: 953490ms (~15 minutes)
  • User: 37531ms | Sys: 5234ms
  • RSS: 0.98GB | Peak: 1.07GB | Commit: 1.40GB
  • Page Faults: 1295216 | Machine: 68.53GB

Bun Crash Report

Bun provided the following crash report URL:
https://bun.report/1.3.10/e_l1423d3cmgkgEuhogD0w3jQk8vtbi+p4Vw7r0U23wN+o5gUmznlOqn4kOwkkqvDCYKERNEL32.DLLo35FCSntdll.dllipmTA0eNorLs8sSc5QyM9TSM4vKiotKFEoS8wpTQUAa8EI/A

Steps to Reproduce

  1. Run Claude Code on Windows 10
  2. Use it for an extended session (~15+ minutes)
  3. Claude Code crashes with the above panic

Expected Behavior

Claude Code should not crash with a Bun runtime panic.

Additional Notes

The crash occurs in the Bun runtime that bundles Claude Code. This may be related to memory corruption or an unexpected code path after prolonged usage.

View original on GitHub ↗

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