Segfault (panic at 0x0) after long session on macOS 26.5.1

Open 💬 1 comment Opened Jun 14, 2026 by Sub-lime-time

Environment

  • Claude Code version: 2.1.177
  • Bundled Bun version: 1.3.14 (2a41ca97)
  • macOS: 26.5.1 (production, Apple Silicon)
  • CPU: Apple M1 Max

What happened

Claude Code crashed with a segfault after approximately 4.3 hours of continuous use.

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

Crash details

Bun v1.3.14 (2a41ca97) macOS Silicon
macOS v26.5.1
CPU: neon fp aes crc32 atomics
Args: "/Users/greg/.local/bin/claude" "--settings" "{...}"
Features: Bun.stderr(2) Bun.stdin(2) Bun.stdout(2) abort_signal(26) fetch(70) jsc spawn(42) standalone_executable yaml_parse(58) claude_code
Elapsed: 15452199ms | User: 73323ms | Sys: 11040ms
RSS: 0.26GB | Peak: 1.18GB | Commit: 0.20GB | Faults: 105 | Machine: 34.36GB

Bun crash report

https://bun.report/1.3.14/M_12a41ca9mgggkEuhogC_u2v81B2ggwlB2yggoB248r9B+m6r9Bm613Qmqt3Quiu3Q2/6tuB+n1spB__A2AA

Notes

  • Latest Claude Code version (2.1.177) — already up to date
  • macOS 26.5.1 is the current production release, not a beta
  • Session was ~4.3 hours long with peak memory of 1.18 GB
  • Session hooks were active (cmux integration)
  • Null pointer dereference suggests a memory issue in the bundled Bun runtime, possibly related to long session duration or macOS 26 compatibility

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗