Claude Desktop cowork/CC-in-Desktop leaks ~19GB kernel non-paged pool memory

Resolved 💬 4 comments Opened Apr 15, 2026 by seanmartinsmith Closed May 25, 2026

Bug

running claude code inside claude desktop (cowork feature) causes a massive kernel non-paged pool memory leak. after ~1-2 hours of use, PoolNonpagedBytes grows to ~19.4GB (normal is 200-500MB). this is kernel-mode memory that can't be freed without a full system restart.

Environment

  • windows 11 home 10.0.26200
  • 32GB RAM
  • NVIDIA GeForce GPU
  • claude desktop latest
  • claude code CLI active in desktop

Reproduction

  1. open claude desktop
  2. use claude code within desktop (cowork)
  3. work for 1-2 hours (multiple sessions, tool calls, etc.)
  4. check memory: task manager shows ~28/32GB used but visible processes only account for ~5GB
  5. verify with powershell:
(Get-CimInstance Win32_PerfFormattedData_PerfOS_Memory).PoolNonpagedBytes / 1GB
# returns ~19.4 (should be 0.2-0.5)

Impact

system becomes unusable - only ~3GB free RAM, everything slows down. only fix is full restart. the leak is in kernel non-paged pool which means it's a driver-level allocation (likely from electron/chromium GPU process) that never gets freed. no user-space process kill can reclaim it.

Diagnostics

PoolNonpagedBytes : 20821811200  (~19.4 GB)
PoolPagedBytes    : 3794968576   (~3.5 GB)
CommittedBytes    : 120590778368 (~112 GB committed)
AvailableBytes    : 3306254336   (~3 GB free)

top processes by memory only accounted for ~5GB total. the 19.4GB non-paged pool is the ghost consumer.

View original on GitHub ↗

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