High memory growth rate in native memory (~18.6 MB/s) on Windows 11
Resolved 💬 4 comments Opened Mar 12, 2026 by michael-florapulse Closed Apr 11, 2026
Description
Experiencing high memory usage from the Claude Code CLI process. A manual heapdump after only ~28 seconds of uptime shows rapid native memory growth.
Diagnostics
- Claude Code version: 2.1.73
- Node.js version: v24.3.0
- Platform: Windows 11 Pro (win32) 10.0.26200
- Trigger: Manual
/heapdump - Uptime at capture: ~28 seconds
Memory Usage
| Metric | Value |
|--------|-------|
| RSS (total process) | 497 MB |
| Heap used | 99 MB |
| Heap total | 45 MB |
| External memory | 67 MB |
| Array buffers | 20 MB |
| Peak malloced memory | 1.27 GB |
Growth Rate
- ~18.6 MB/second (~64 GB/hour)
Analysis (from diagnostics JSON)
- Native memory > heap — leak may be in native addons (node-pty, sharp, etc.)
- High memory growth rate: 63927.5 MB/hour
Steps to Reproduce
- Launch Claude Code on Windows 11
- Run
/heapdumpafter ~30 seconds - Observe high RSS and native memory growth rate in diagnostics JSON
Expected Behavior
Memory growth rate should be minimal when idle or during light usage, not ~18.6 MB/s.
Additional Context
The diagnostics point to native memory (external > heap), suggesting the leak is in a native addon rather than JS-land.
This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗