Bun v1.3.10 panic crash on Windows with multiple local agents

Bug Description

Claude Code crashes with a Bun runtime panic (switch on corrupt value) on Windows when running multiple local agents in long sessions.

Error Message

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

Environment

• Claude Code version: 2.1.51
• Bun version (bundled): v1.3.10 (1423d3c8)
• OS: Windows 11 Pro 10.0.26100 (Windows x64 baseline)
• CPU: sse4.2 avx avx2
• Machine RAM: 34.25GB

Reproduction Details

• Local agents running: 3 concurrent agents
• Session duration at crash: ~10,869,681ms (~3 hours)
• Memory at crash: RSS: 0.86GB | Peak: 1.59GB | Commit: 3.27GB
• Args: C:\Users\<user>\.local\bin\claude.exe
• Features: Bun.stderr(2) Bun.stdin(2) Bun.stdout(2) abort_signal(131) fetch(10929) jsc spawn(168) standalone_executable process_dlopen(3) yaml_parse(571)

Steps to Reproduce

1. Launch Claude Code on Windows
2. Run a task that spawns 3 local agents
3. Let the session run for an extended period (~3 hours)
4. Bun panics with "switch on corrupt value" memory corruption

Bun Crash Report

A crash report was generated by Bun's crash reporter. This appears to be a known class of Bun memory corruption bugs on Windows under sustained multi-agent workloads.

Expected Behavior

Claude Code should not crash during long-running multi-agent sessions. Ideally, the bundled Bun version should be updated to a more recent release that includes fixes for Windows memory corruption issues.

Workarounds

• Reducing concurrent agent count (1-2 instead of 3)
• Restarting Claude Code periodically during long sessions
• Breaking work into smaller sessions