[BUG] High memory usage (50.4GB)

Status Fixed / completed
Reported on v2.1.72
Maintainer reply None cached
Activity 10 comments · opened Mar 11, 2026 · closed Mar 12, 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?

I had Claude Code created me network monitoring node using Python, and after that Claude Code crashed with error on the side says "High memory usage (50.4GB) ".
The monitoring node isn't running automatically, but every time I open a Claude Code session a high memory usage indicator shows up and memory usage keeps growing.
The issue only happened on my main PC, I don't see such issue on my second computer

b5e6db92-22e2-4b7d-aa23-a3a7921359a3-diagnostics.json

What Should Happen?

Claude Code shouldn't use that much RAM

Error Messages/Logs

Steps to Reproduce

Couldn't reproduce it on my second computer

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.72 (Claude Code)

Platform

Anthropic API

Operating System

Other Linux

Terminal/Shell

Other

Additional Information

Updating to the latest version 2.1.74 resolved the issue.

View original on GitHub ↗

10 Comments

davis-allen-disney · 5 months ago

All of a sudden (today) I am getting similar issues on my MacOS. Claude crashes frequently. 50GB+ memory usage

dabd44a2-1a27-48a9-ad26-370bba8b1574-diagnostics.json

I also have a heap snapshot file that I can't seem to attach to this ticket.

github-actions[bot] · 5 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/31414
  2. https://github.com/anthropics/claude-code/issues/33280
  3. https://github.com/anthropics/claude-code/issues/33211

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

noahgorstein · 5 months ago
All of a sudden (today) I am getting similar issues on my MacOS. Claude crashes frequently. dabd44a2-1a27-48a9-ad26-370bba8b1574-diagnostics.json I also have a head snapshot file that I can't seem to attach to this ticket.

same here!

mosamaasif · 5 months ago

Yes. Restarted a session today and suddenly getting the same error!

lagtac · 5 months ago

same here. where can we submit a heapdump?

chaunsin · 5 months ago

me too!
my snapshot

  • version: 2.1.72

<img width="2094" height="288" alt="Image" src="https://github.com/user-attachments/assets/664c1dcd-6b48-4c71-9e3d-5d73511245a6" />

<img width="1278" height="994" alt="Image" src="https://github.com/user-attachments/assets/cc5df99b-8ba5-4794-90cc-12b22bf8fefd" />

pradeeshjayachandran · 5 months ago

can you try the latest version - 2.1.74? I had the same issue with v2.1.72 running on Ubuntu 25.10. After the update, I don't see the high memory usage warning and the heap dump looks good.

Montadher-M · 5 months ago
can you try the latest version - 2.1.74? I had the same issue with v2.1.72 running on Ubuntu 25.10. After the update, I don't see the high memory usage warning and the heap dump looks good.

Yeah, updating to 2.1.74 resolved the issue.
Thanks mate

kamilpajak · 5 months ago
> can you try the latest version - 2.1.74? I had the same issue with v2.1.72 running on Ubuntu 25.10. After the update, I don't see the high memory usage warning and the heap dump looks good. Yeah, updating to 2.1.74 resolved the issue. Thanks mate

Updating to 2.1.74 initially fixed the high memory usage for me, but the issue has come back after a few days.

Environment:

  • Debian 12, 12 GB RAM
  • Claude Code 2.1.74

claude is idle in an empty directory, but its RAM usage keeps growing over time until it gets close to all available memory.

github-actions[bot] · 5 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.