Thrum

Why is a node process using so much CPU or memory on my Mac?

Last reviewed: 19 November 2026. Paths and parent processes of running node processes checked on macOS 26.3.1.

A process named node is a Node.js program running a JavaScript file, so the question is which program: a development server, a build or test runner, a command-line tool, or a helper bundled inside another app. Its full command line names the script, and its parent process shows what started it. Once you know the program, stop or fix that program rather than the runtime.

node at a glance

node
Made byOpenJS Foundation (Node.js); copies are bundled by many apps
TypeJavaScript runtime process
Runs asyour user
Can you quit it?Yes, but the server, build or tool it is running stops. Find out what it is first.

What is node?

Node.js runs JavaScript outside a browser. Every npm run, npx command, dev server, bundler, linter and many editor extensions start node processes, and so do apps that ship their own copy of Node.js inside their bundle. On the Mac used for checking, node ran from an nvm folder in the home directory and from inside two different apps' bundles.

The path tells you which installation it is: Homebrew uses /opt/homebrew/bin/node on Apple silicon, nvm uses ~/.nvm/versions/node/<version>/bin/node, and a node inside /Applications/<App>.app belongs to that app.

Is node safe?

node itself is a normal runtime. Whether a particular node process is wanted depends on the script it runs, which ps -o args= shows. A node you did not start and cannot link to an app or tool you use deserves a closer look.

Why does node use so much CPU, memory and network?

How much CPU is normal for node?

A dev server idle between edits sits near 0% CPU. Builds and installs use a lot of CPU for as long as they run.

Memory depends on the program; editor helpers and dev servers commonly stay in the hundreds of megabytes.

How do you find out what a node process is running?

  1. Read its command line. Run ps -o pid,ppid,args -p <PID> with the PID from Activity Monitor. The arguments show the script or package, for example a path inside node_modules/.bin.
  2. Find its parent. Run ps -o comm= -p <PPID> with the PPID from the line above, or double-click the process in Activity Monitor. The parent might be your shell, npm, an editor or an app.
  3. Find its working folder. Run lsof -a -p <PID> -d cwd to see which project folder it was started in.
  4. Stop it from where it started. Press Control-C in the Terminal window running it, stop the task in your editor, or quit the app that owns it. Use Quit in Activity Monitor only if nothing else works.
  5. Profile it if it is yours. Run the script with node --prof and process the log with node --prof-process, as Node.js's profiling guide describes, to see which functions use the CPU.

When should you worry about node?

A node process you cannot trace to a tool, project or app, especially one that starts at login and sends network traffic, should be investigated: check its path, script and parent, and look in ~/Library/LaunchAgents for a job that starts it.

A node process whose parent is launchd (PID 1) was either started by a launch agent or left running by a terminal, editor or tool that has since closed. Quitting a leftover one is fine once you know what it is.

How do you check node in Activity Monitor and Terminal?

Open Activity Monitor (Applications > Utilities), and type node in the search field. The CPU tab shows its % CPU. The Memory tab shows its Memory. The Network tab shows its Sent Bytes and Rcvd Bytes. Double-click the row for its parent process, memory details and open files.

In Terminal, the first command lists every node process with its PID, user, CPU and memory (RSS is resident memory in kilobytes). nettop shows its live network traffic.

ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'node' | grep -v grep
nettop -p node

How can Thrum help with node?

Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when node is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. Click node in the list for its PID, threads and memory, and Quit or Force Quit it after a confirmation.

Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.

Questions about node

Why do I have node running when I never installed Node.js?

Some apps bundle their own copy of Node.js. The path in the command line shows the app it belongs to.

Is it safe to quit node in Activity Monitor?

Usually, but unsaved work in that program is lost and a server it runs stops. Stopping it from the terminal or tool that started it is cleaner.

Sources