Memory leak: idle sessions consume excessive RAM (27GB+)

Resolved 💬 3 comments Opened Feb 2, 2026 by jribenfors Closed Feb 6, 2026

Description

Idle Claude Code sessions appear to accumulate memory over time, eventually triggering the Linux OOM killer despite having 32GB RAM and no active work being performed.

Evidence

From dmesg:

[10021.769809] Out of memory: Killed process 5052 (claude) total-vm:75490280kB, anon-rss:28685704kB, file-rss:0kB, shmem-rss:24kB, UID:1000 pgtables:57800kB oom_score_adj:200

Key stats:

  • anon-rss: ~27.4 GB actual RAM consumed
  • total-vm: ~72 GB virtual memory requested
  • State: Idle (no active tasks running)

Steps to Reproduce

  1. Open one or more Claude Code terminal sessions
  2. Leave them idle overnight (no active conversations or tasks)
  3. System runs out of memory despite no active work

Expected Behavior

Idle sessions should have minimal memory footprint. 27GB for idle sessions is excessive.

Environment

  • OS: Linux 6.17.0-8-generic
  • RAM: 32 GB
  • Claude Code: CLI

View original on GitHub ↗

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