Bun runtime segfault crash during long session

Description

Claude Code crashes with a Bun runtime segmentation fault after extended usage (~32 minutes session).

Crash Details

Bun v1.3.5 (1e86cebd) Linux x64 (baseline)
Linux Kernel v6.14.0 | glibc v2.39
CPU: sse42 popcnt avx avx2
Args: "claude" "--dangerously-skip-permissions" "--resume"
Features: Bun.stderr(2) Bun.stdin(2) Bun.stdout(2) abort_signal(30) fetch(2515) jsc spawn(431) standalone_executable process_dlopen(2) 
Builtins: "bun:main" "node:assert" "node:async_hooks" "node:buffer" "node:child_process" "node:constants" "node:crypto" "node:domain" "node:events" "node:fs" "node:fs/promises" "node:http" "node:https" "node:module" "node:net" "node:os" "node:path" "node:path/win32" "node:perf_hooks" "node:process" "node:querystring" "node:stream" "node:timers/promises" "node:tls" "node:tty" "node:url" "node:util" "node:zlib" "node:worker_threads" "undici" "ws" "node-fetch" "node:inspector" "node:http2" "node:diagnostics_channel" 
Elapsed: 1913259ms | User: 620078ms | Sys: 57413ms
RSS: 0.02ZB | Peak: 2.83GB | Commit: 0.02ZB | Faults: 0 | Machine: 0.13TB

panic(main thread): Segmentation fault at address 0x0
oh no: Bun has crashed. This indicates a bug in Bun, not your code.

Environment

• Claude Code Version: 2.1.4
• Bun Version: 1.3.5 (bundled)
• OS: Linux (Ubuntu, kernel 6.14.0-37-generic)
• glibc: 2.39

Steps to Reproduce

1. Start a Claude Code session with claude --dangerously-skip-permissions
2. Work on a complex multi-file refactoring task (in this case, splitting a large route file into multiple domain-specific files)
3. Session runs for ~30+ minutes with multiple tool calls (file reads, edits, bash commands)
4. Crash occurs with segmentation fault at address 0x0

Additional Context

• Session involved heavy file operations (reading/writing ~12 files)
• Peak memory usage reached 2.83GB
• The crash appears to be in Bun's memory management, not Claude Code application logic
• Bun's own crash report link: https://bun.report/1.3.5/B_11e86cebmgEuhogCk0iruE+ypR__________0rsk/Dqli3jFstpglEyjgy/Cogy97C6s3xgEwq1l7Cylw21CA2AA

Expected Behavior

Session should remain stable during long-running operations, or gracefully handle memory pressure without crashing.

Suggested Actions

1. Consider reporting upstream to Bun team with the crash report
2. Investigate if there are memory leaks in long sessions
3. Consider adding session checkpointing to recover from crashes more gracefully