[BUG] exceptional memory usage since v2.0.8
Status Closed — not planned
Maintainer reply None cached
Activity 12 comments · opened Oct 5, 2025 · closed Jan 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?
each instance of claude code is using anywhere from 2.5-3GB to 8GB of RAM, on a MacBook Pro M4 Pro with built-in GPU. nothing has changed on my macbook other than claude code auto-update, whenever that happened. See this:
<img width="861" height="686" alt="Image" src="https://github.com/user-attachments/assets/96ebda64-1956-4653-b63c-d26cedaec3e8" />
What Should Happen?
if 1 claude code terminal takes up on an average 4-5 GB of Memory, MacBooks are not just running out of battery but there's not much we can do with claude code in 1 terminal !
Error Messages/Logs
provided from activity monitor all details.
Steps to Reproduce
just launch claude code in macos terminal or warp terminal, then watch activity monitor.
Claude Model
Sonnet (default)
Is this a regression?
Yes, this worked in a previous version
Last Working Version
2.0.8
Claude Code Version
2.0.8 (Claude Code)
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
_No response_
12 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
<--- Last few GCs --->
[2184614:0x33dc9000] 694035870 ms: Mark-Compact 4081.4 (4111.3) -> 4064.5 (4121.4) MB, pooled: 0 MB, 122.74 / 0.09 ms (average mu = 0.397, current mu = 0.416) allocation failure; scavenge might not succeed
[2184614:0x33dc9000] 694036016 ms: Mark-Compact (reduce) 4081.5 (4125.0) -> 4073.0 (4095.0) MB, pooled: 0 MB, 28.58 / 0.01 ms (+ 62.3 ms in 217 steps since start of marking, biggest step 5.2 ms, walltime since start of marking 134 ms) (average mu = 0.390
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----
1: 0xf41253 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [claude]
2: 0x1388b50 v8::Utils::ReportOOMFailure(v8::internal::Isolate, char const, v8::OOMDetails const&) [claude]
3: 0x1388c3f v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate, char const, v8::OOMDetails const&) [claude]
4: 0x1621705 [claude]
5: 0x1621732 [claude]
6: 0x1621a2a v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector, v8::base::TimeTicks) [claude]
7: 0x1631f4a [claude]
8: 0x16362f0 [claude]
9: 0x20c8ff1 [claude]
Aborted
Yeah, wow, mine dumped core too:
"if 1 claude code terminal takes up on an average 4-5 GB of Memory, MacBooks are not just running out of battery but there's not much we can do with claude code in 1 terminal !"
Isn't it great to live in 2025 where we have the literal holy grail of AI at our fingertips but also everything is javascript and garbage collection?
<img width="2144" height="1504" alt="Image" src="https://github.com/user-attachments/assets/b87d11e1-2f58-4766-87dc-251d4823aef9" /> running into the same issues if switching between repository with opening claude extension in Cursor
I'm also seeing 1-2 GB of memory usage per session. this is insane.
<img width="745" height="671" alt="Image" src="https://github.com/user-attachments/assets/ece831b4-b220-4e1e-97fc-41c808e4102b" />
very high amounts of memory being used
exactly the same issue when runing claude code inside Cursor
this seems to resolved by
2.0.33! im seeing like 300mb of ram usage compared to 1.5-2 gigs on my macbook pro m4This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.
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.