SIGABRT crash when transitioning to extra usage (v2.1.68)

Resolved 💬 2 comments Opened Mar 4, 2026 by GaudianVivere Closed Apr 2, 2026

Claude Code crashes with SIGABRT when transitioning to "extra usage"

Version

  • Claude Code: 2.1.68
  • Node.js: v24.13.1
  • macOS: 15.7.4 (24G517)
  • Hardware: MacBookPro15,1 (Intel x86_64)

Description

Claude Code consistently crashes with SIGABRT (abort trap 6) when the session transitions from included usage to "extra usage". The message "Now using extra usage" appears briefly before the process terminates.

This happens:

  • On every new session start when the billing period quota is already exhausted
  • Mid-session when the quota runs out during a conversation
  • Extra usage IS enabled and configured in billing settings

Reproduction steps

  1. Use Claude Code until included quota is exhausted
  2. Start a new session or continue until "Now using extra usage" appears
  3. Process immediately aborts with zsh: abort claude

Crash report summary

Exception: EXC_CRASH / SIGABRT
Termination: Abort trap: 6 (self-terminated by process 2.1.68)
ASI: libsystem_c.dylib — abort() called
Faulting thread: 18

The process terminates itself (byProc: "2.1.68") — this is not an OS kill or OOM. The abort() is called intentionally within the Claude Code binary.

Frequency

9 crash reports in a single day (2026-03-04), all with identical signature.

Expected behavior

When "extra usage" is enabled and billing is set up, the session should continue seamlessly after the included quota is exhausted.

Workaround

None found. Waiting for the billing cycle to reset is the only way to start new sessions.

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗