# Nx 21.4.0: node processes linger at 100% CPU after ending the session
## What was going on
On Nx 21.4.0, after shutting down the dev stack, node processes linger and keep consuming 100% CPU; nx reset --only-daemon kills some but not all of them. Over a day of up/down cycles this leaves multiple node processes spinning and grinds the machine to a halt. The orphaned processes come from Nx not cleaning up child processes it spawned (e.g. wrapped dev commands) when the session ends via Ctrl+C.
## The fix that worked
This is an Nx bug in child-process cleanup on session exit. Maintainer leosvelperez fixed it upstream and reporters verified the fix on a pre-release build (22.7.0-pr.33655.12b0dd7): no orphaned processes, continuous targets no longer marked failed on Ctrl+C, and no startup exception. Upgrade Nx to a release containing that fix. Until then, nx reset --only-daemon only stops the daemon; find and kill the leftover node PIDs manually (e.g. via Activity Monitor or pkill -f nx) to reclaim the CPU.
## Where this came from
https://github.com/nrwl/nx/issues/32438