Why is Google Chrome Helper using so much CPU on my Mac?

Why Chrome has so many helpers

Google’s Chrome developer documentation describes the processes: a browser process that runs the app itself, renderer processes for web pages, a GPU process for graphics, plus extension and utility processes. Chrome tries to give each site its own process, including frames embedded in a page, and when it hits its limit it runs several tabs from the same site in one process.

Google’s reason is that if one tab stops responding, you can close it and keep the others. Many helpers with only a few tabs open is normal; the number of helpers isn’t the problem, one busy helper is.

The one-minute check

1. In Chrome, click the ⋮ menu at the top right, then More tools, then Task manager. Google says it lists the processes running and how much CPU and memory each is using: each tab, each extension, and Chrome’s own GPU and browser processes.
2. Click the CPU column to sort it and watch for half a minute. The row that stays at the top is the one to deal with.
3. To match it with Activity Monitor, open Activity Monitor, choose View, All Processes, Hierarchically. Apple says this shows which processes belong to which, so the helpers appear grouped under Google Chrome.

% CPU counts each core as 100%, in both windows, so a helper can show more than 100% on a Mac with several cores. Short spikes while a page loads are normal; a high number that stays is what you’re looking for.

Common causes, and what to do

A busy tab

A page with video, animation, a web app that keeps working in the background, or a page with a bug can keep its renderer busy even when you aren’t looking at it.

What to do: close the tab. If it won’t respond, select it in Chrome’s Task manager and click End process; Google’s help describes this for a tab, window or extension that isn’t working.

An extension

Extensions run in their own processes and appear by name in Task manager, so a busy one is easy to spot there.

What to do: turn off or remove extensions you don’t need. Google’s troubleshooting steps include uninstalling extensions you don’t use. If you see one you don’t remember installing, Google’s help also covers spotting and removing unwanted software on a Mac.

The GPU process

Google Chrome Helper (GPU) handles graphics work for all tabs, so it’s busy when anything on screen is changing: video, animation, a game, or scrolling a heavy page. Find the tab behind it the same way and close it. Google suggests turning off “Use hardware acceleration when available” (⋮, Settings, System) for crashes and display problems, not as a CPU fix, so leave it on unless you see those.

Lots of tabs in the background

Chrome has two settings for this in ⋮, Settings, Performance. Google says Memory Saver deactivates tabs you aren’t using and reloads them when you go back, and Energy Saver, which turns on when the Mac is unplugged or the battery is low, stops eligible CPU-intensive background tabs. Chrome may also show a performance alert offering to deactivate tabs; click Fix now to accept.

Still high with almost nothing open

Quit Chrome with Command-Q and reopen it, as Google’s troubleshooting suggests. If it comes back, open Task manager again straight away; whatever reopened with your tabs is the one.

What not to do

• Don’t quit helpers at random in Activity Monitor. Each one is a tab, an extension or part of Chrome, and Activity Monitor doesn’t say which. Chrome’s Task manager ends the right one.
• Don’t buy a “CPU fix” app. The helper is running a page or extension you can name in Task manager and close yourself.

Keep an eye on it from the menu bar

A forgotten tab can sit at high CPU for hours before you notice the fans or the battery. Multimeter keeps the totals in the menu bar, so you notice when the Mac stays busy:

• CPU: total use across all cores, every 3 seconds on power and about every 6 on battery. Yellow above 70%, red above 90% by default, with an optional notification when it goes critical. The Sparkline face shows whether it rose when you opened a page.
• Thermal pressure: Nominal, Fair, Serious or Critical, the state macOS uses to decide when to hold performance back. It’s a state, not degrees.

Multimeter shows totals, not per-process lists, so it won’t name Chrome or the tab; it tells you when to open Chrome’s Task manager. Five live meters use about 3% CPU, and they pause while the displays sleep.