Bun segfault on Windows after long idle sessions with sleep/wake cycles
Resolved 💬 5 comments Opened Mar 17, 2026 by ElliotDrel Closed Jun 1, 2026
Environment
- Claude Code v2.1.77
- Bun v1.3.11 (bundled)
- Windows 11 Pro 10.0.26200
- 16.92GB RAM
Description
Two out of five concurrent Claude Code sessions crashed with Bun segfaults after being left idle for ~24 hours on Windows 11. The laptop went through multiple sleep/wake cycles during this period. Three sessions survived.
Both crashes show identical signatures — segmentation faults in KERNEL32.DLL/ntdll.dll with high memory commit (~4.5-4.8GB) and millions of page faults.
Crash Dumps
Crash 1 (Elapsed: 84520518ms, RSS: 0.92GB, Commit: 4.84GB):
Segmentation fault at address 0x5CA6C010000
Crash 2 (Elapsed: 85253911ms, RSS: 1.34GB, Commit: 4.51GB):
Segmentation fault at address 0x44924010000
Suggestions
- Consider upgrading the bundled Bun version if a fix lands upstream
- A heartbeat or watchdog mechanism could detect and gracefully recover from runtime crashes, preserving session state
- Document that long idle sessions across sleep/wake cycles on Windows may crash
Upstream
Filing corresponding issues on oven-sh/bun with the bun.report crash links.
This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗