Bun panic crash: 'switch on corrupt value' during Explore agents on Windows 11 #27086
Closed as duplicate
Description
Bug Report
Environment
- Claude Code version: v2.1.49
- Model: Opus 4.6 · Claude Max
- OS: Windows 11 (win11_dt)
- CPU: SSE4.2, AVX, AVX2
- Bun version: v1.3.10 (1423d3c8)
- Architecture: Windows x64 (baseline)
- Machine RAM: 33.96 GB
Steps to Reproduce
- Install Claude Code on Windows via
irm https://claude.ai/install.ps1 | iex - Run
claude --dangerously-skip-permissionsin a project directory - Ask Claude to explore a project:
"обнови проект с гитхаба, изучи детально, составь список сервисов, которые используются в проекте"
- Claude launches 2 Explore agents in parallel
- After ~3 minutes of work, Bun crashes with a panic
Expected Behavior
Claude should complete the project exploration and return results without crashing.
Actual Behavior
Bun runtime panics with switch on corrupt value error after ~203 seconds of execution.
Crash Details
Bun v1.3.10 (1423d3c8) Windows x64 (baseline)
Windows v.win11_dt
CPU: sse42 avx avx2
Elapsed: 202923ms | User: 6328ms | Sys: 2875ms
RSS: 0.73GB | Peak: 0.92GB | Commit: 1.04GB | Faults: 446576 | Machine: 33.96GB
panic(main thread): switch on corrupt value
oh no: Bun has crashed. This indicates a bug in Bun, not your code.
Crash Report Link
Memory Usage at Crash
| Metric | Value |
|---|---|
| RSS | 0.73 GB |
| Peak | 0.92 GB |
| Commit | 1.04 GB |
| Page Faults | 446,576 |
Context
- First launch after fresh installation on Windows 11
- The crash occurred while running 2 Explore agents concurrently (parallel codebase exploration)
- The git pull + initial bash command succeeded before the crash
- Project being explored: a Node.js/TypeScript project (~115 test files, ~180 source files)
Notes
- This appears to be a Bun runtime issue (
switch on corrupt valuepanic), possibly triggered by concurrent agent operations under memory pressure on Windows - The crash is in Bun's main thread, not in user code