Bun segfault after ~21h session (v2.1.49, Bun 1.3.10, Linux x64)
Resolved 💬 2 comments Opened Feb 21, 2026 by aaronjohnson Closed Feb 22, 2026
Description
Claude Code crashed with a Bun segfault during a long-running planning session (~21 hours elapsed). The session involved generating a large plan output (multi-hundred-line RFC plan with tables and code blocks).
Environment
- Claude Code: v2.1.49
- Bun: v1.3.10 (1423d3c8)
- Platform: Linux x64 (baseline)
- Kernel: v6.6.99
- glibc: v2.36
- CPU: sse42 popcnt avx avx2
Crash Details
Elapsed: 77170796ms (~21.4 hours)
User: 736332ms | Sys: 239130ms
RSS: 0.02ZB | Peak: 0.66GB | Commit: 0.02ZB | Faults: 50
panic(main thread): Segmentation fault at address 0x7FFEC6F5D9A5
Notable
- RSS reports 0.02 ZB (zetabytes) — clearly corrupted memory accounting, likely related to the crash
- Peak RSS was 0.66GB which is plausible; the 0.02ZB values suggest the memory tracker overflowed or was corrupted before the segfault
- Crash occurred at a tool permission prompt (Bash command approval dialog), not during heavy computation
- The auto-generated crash report URL was visited:
bun.report/1.3.10/B_11423d3c...
Reproduction
Difficult to reproduce exactly. General conditions:
- Start a Claude Code session
- Enter plan mode with a large, multi-section plan (~350 lines with tables, code blocks, Sanskrit/Devanagari Unicode)
- Leave the session running for ~21 hours
- Interact with a tool permission prompt
The segfault may be related to the long elapsed time, memory corruption (suggested by the ZB-scale RSS), or possibly Unicode handling in the terminal output.
Bun Crash Metadata
Features: Bun.stderr(2) Bun.stdin(2) Bun.stdout(2) abort_signal(73) fetch(496) jsc spawn(138) standalone_executable process_dlopen(2) yaml_parse(2)
Builtins: "bun:main" "node:assert" "node:async_hooks" "node:buffer" "node:child_process" "node:constants" "node:crypto" "node:events" "node:fs" "node:fs/promises" "node:http" "node:https" "node:module" "node:net" "node:os" "node:path" "node:path/posix" "node:path/win32" "node:perf_hooks" "node:process" "node:stream" "node:timers/promises" "node:tls" "node:tty" "node:url" "node:util" "node:zlib" "node:worker_threads" "undici" "ws" "node:http2"This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗