[BUG] Silent crash on Windows — no error output

Resolved 💬 4 comments Opened Mar 10, 2026 by MichaelCharles Closed Mar 13, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

Claude Code silently exits (returns to shell prompt) with no error message, no stack trace, and no crash dump. This seems to happen randomly, although I was able to consistently make it happen by trying to resume a larger conversation. It happened mid-session after 530 messages creating a 1.2MB session file. When attempting to /resume that session, it consistently crashes.

I've also been experiencing random such crashes even when the context is as low as 12%. When I attempt to resume the sessions it crashes.

What Should Happen?

It shouldn't randomly crash.

Error Messages/Logs

# What I've checked
  - No entries in Windows Event Log or Windows Error Reporting
  - No crash dumps in %LOCALAPPDATA%\CrashDumps
  - Debug log (`~/.claude/debug/`) shows no errors — the log simply stops mid-operation with no REPL:unmount
  - Memory was not an issue: 6GB free RAM, Node heap at 2GB limit, tokens at 74K/167K threshold

Steps to Reproduce

  1. Use CC on Windows for an extended session
  2. Session will silently crash at some point
  3. Attempting /resume on the crashed session will also silently crash

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.70

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Windows Terminal

Additional Information

_No response_

View original on GitHub ↗

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