[BUG]

Resolved 💬 3 comments Opened Dec 18, 2025 by emilzo Closed Dec 22, 2025

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?

[Windows 11/10] CLI crashes with rapid text scrolling after extended use - possible memory leak (v2.0.72)
Body:

Environment

  • Claude Code version: 2.0.72
  • OS: Windows 11
  • Terminals tested: CMD, PowerShell, VS Code integrated terminal (issue occurs in all)
  • RAM: 32GB + 32GB virtual memory
  • Session length: 10-20 hours typical

Problem Description

After extended use (never at session start, always after several minutes of work), the CLI crashes with a distinctive pattern:

  1. Text starts scrolling extremely fast on screen
  2. Terminal freezes completely
  3. Must kill the process manually (Ctrl+C doesn't work)
  4. Context is lost or corrupted

Frequency

  • ~10+ crashes per 10-20 hour session
  • Severely impacts productivity
  • Ongoing for months across multiple versions

Behavior Details

Before crash:

  • Rapid uncontrolled text scrolling
  • No user input possible

After crash:

  • Sometimes: can copy last visible instructions and recover context manually
  • More often: session resumes with context from minutes/hours earlier or even previous sessions (context corruption)

What I've tried

  • Different terminals (CMD, PowerShell, VS Code integrated) - same issue
  • Adjusting virtual memory settings - no effect
  • System has 32GB RAM + 32GB virtual - resources not the issue

Suspected cause

The pattern (never at start, always after extended work) suggests:

  • Memory leak in the CLI process
  • Context buffer overflow
  • Rendering issue when context grows large

Impact

This has been happening for months and significantly affects daily work. Sessions of 10-20 hours are common for my workflow, and losing context 10+ times per session is extremely disruptive.

Request

  • Investigation into memory usage over time
  • Possible automatic context compaction before critical thresholds
  • Better crash recovery that preserves recent context accurately

System Info

Happy to provide additional logs or run diagnostic commands if needed.

Note: I have plenty diferent machines, setups, workflows. I here to help.

What Should Happen?

[Windows 11/10] CLI crashes with rapid text scrolling after extended use - possible memory leak (v2.0.72)
Body:

Error Messages/Logs

Steps to Reproduce

  1. The error happens after some work, never at first hour of intensive work.

Claude Model

Opus

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

C:\AshtonProjects\Galman2\Replit-onegocio>claude -v 2.0.72 (Claude Code)

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

VS Code integrated terminal

Additional Information

no, i have nothing. I will try to send a movie of a screen sharing session.

View original on GitHub ↗

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