Guide

How to investigate Chrome CPU and memory usage

Use Chrome's task manager to distinguish tabs and extensions, then compare one change at a time against the same workload.

Capture a comparable baseline

Save forms and downloads before investigating. Record which tabs, extensions, calls, media and developer tools are open. Observe the symptom over more than one sample. Comparing a video call with an idle browser is not a useful before-and-after test.

Multiple chrome.exe processes are expected in a browser with separate tasks. A process count alone does not diagnose malware or a memory leak. Verify unexpected executables by their full path and publisher signature before treating a name as an identity.

Find the browser task doing the work

Open Chrome's own task manager from its menu; where supported, Shift+Esc opens it directly. Inspect the tasks associated with tabs, extensions and background work. Sort by the resource relevant to the symptom. Google's troubleshooting documentation recommends ending unwanted browser tasks, but ending one can interrupt work in that tab.

Close one unneeded tab or disable one unnecessary extension, then repeat the same workload. If the symptom disappears, re-enable the extension or reopen the task to test whether the behavior returns. A repeatable relationship is stronger evidence than a single coincidental improvement.

Use Memory Saver with the right expectations

Chrome's performance settings can deactivate inactive tabs to release memory. Returning to an inactive tab can reload it. Sites doing audio, calls, screen sharing, downloads or form work may remain active. Those exceptions explain why enabling Memory Saver does not make every background tab disappear.

Use the option to keep selected sites active when the workflow needs it. Test the effect on your own set of tabs. Memory Saver is a resource-management feature; it does not fix every extension defect or guarantee a particular RAM reduction.

Escalate without losing the browser profile

Update Chrome through its supported update flow and repeat the test. If an extension is implicated, check its publisher and remove it through Chrome's extension manager when appropriate. Keep a note of the extension name and the test result.

Avoid downloading unofficial memory cleaners or deleting the profile directory as a first step. Account data, local site storage and unsynchronized work can be lost. If the issue remains, collect the browser version, task name, affected site, steps to reproduce and whether the same task recurs after a restart.

Sources

Editorial ownership: Feex. No independent review date is recorded. How we research.

Google Chrome Help: Speed up Chrome · Primary documentation. The diagnostic sequence is Feex editorial guidance; it is not a measured diagnosis of your PC.
Google Chrome Help: Performance settings · Primary documentation. The diagnostic sequence is Feex editorial guidance; it is not a measured diagnosis of your PC.
Microsoft Sysinternals: Sigcheck · Primary documentation. The diagnostic sequence is Feex editorial guidance; it is not a measured diagnosis of your PC.

Report a correction to Feex

Was this guide useful?

A yes or no is enough. Pick a reason if you want, or add a short note.