When the whole computer starts feeling sluggish, most people open the Windows Task Manager, squint at the list, and give up. The list says “Google Chrome” fifteen times over, and nothing in it tells you which of your fifteen tabs is the one doing the damage.
Chrome knows exactly which tab that is. It just doesn’t tell you — until you press the right key combination.
Why the Windows Task Manager can’t name the culprit
Chrome gives every tab, extension and background process its own separate process. That’s deliberate: if one tab crashes, the rest of your browser survives. But the operating system only sees the raw processes, so Task Manager shows you a wall of identical “Google Chrome” entries with a memory number next to each and no way to tell which one is Gmail, which one is that spreadsheet, and which one is an extension you forgot you installed in 2023.
Chrome’s own task manager solves this by naming things properly. Instead of fifteen identical entries, you see the actual page title of each tab and the actual name of each extension, with a memory figure beside it. It is the same machine’s same browser — the view just respects the question you are actually asking.
Opening it takes one keyboard shortcut
With Chrome focused, press Shift + Esc. A small window pops up listing everything the browser is running.
If that shortcut is claimed by something else on your system, you can get there from the three-dot menu: More tools → Task Manager. On a Mac, Shift + Esc isn’t bound, so it’s under the Window menu instead.
Read it like a hit list
Click the Memory footprint column header and the list sorts itself. The hungriest processes rise to the top, and that alone usually answers the question.
Three things tend to stand out. First, media-heavy tabs: a streaming site, a video call, a social feed that’s been open since morning. Second, web apps: Gmail, Google Docs, a cloud spreadsheet — these quietly accumulate data the longer they stay open and are often the biggest single entries on the list. Third, something you didn’t expect, which brings us to extensions.
When you find the offender and it’s just a tab you’re done with, closing the tab from the browser works. But if the tab has locked up entirely, select it in the task manager and click End process. That kills only that tab’s process — everything else keeps running. Save anything important first, because an unsaved form on that tab won’t survive.
Extensions are often the real surprise
Most people assume tabs are the problem, and tabs certainly add up. But extensions keep running for your entire browsing session, whether you use them or not. Some inject code into every page you visit, so their cost quietly grows with your tab count while they appear as a single line in the list.
A password manager, a grammar checker and an ad blocker can easily cost more memory between them than ten open pages. If an extension you barely touch is near the top of the list when sorted by memory, that’s a reasonable candidate to remove — or at least to disable and see if anything you care about breaks.
Edge users: you have the same tool under a different menu
Microsoft Edge is built on the same foundation as Chrome, and it ships the same idea: three-dot menu → More tools → Browser task manager. Shift + Esc works here too on Windows and Linux.
Edge’s version has one trick Chrome’s doesn’t advertise as clearly: you can select several tabs at once and end their processes in one click, which is genuinely handy on those days when the browser has become a fifteen-tab archaeological dig.
Firefox does it its own way
In Firefox, type about:processes into the address bar — or use the menu (More Tools → Task Manager), or Shift + Esc — and you get the equivalent page. Tabs, extensions and browser processes are listed with memory and CPU figures, and you can sort by clicking the headers.
One Firefox quirk worth knowing: all extensions share a single content process, so the Processes page only shows you the combined cost of every add-on. If an extension is the suspect and you want to see which one, the separate about:performance page breaks them out individually. Hover over any item in the Processes page and the action button lets you close a tab outright or unload its contents — freeing its memory while keeping the tab itself in place.
Two extra columns worth turning on
Right-click anywhere on the column headers in Chrome or Edge and a longer list of optional columns appears. Two of them earn their place.
JavaScript memory shows how much a page is holding in its own script heap — that’s where a badly behaved web app usually shows itself, since a page can leak memory internally while its headline memory figure looks unremarkable. Idle wake ups is the one laptop owners should care about: a background process that keeps waking up drains the battery even when its memory usage looks perfectly innocent. You only need to enable these once; the browser remembers your choices.
Where this tool stops helping
A few honest limits. Don’t end the process called Browser — that’s the browser itself, and ending it takes everything down. If you regularly find one extension near the top of the memory list, ending its process only buys you until the next session; the actual fix is removing or replacing the extension. And if the offending tab is an article buried in heavy ads and pop-ups, you might not need the task manager at all — your browser’s reader mode strips the page down to the text and the difference in weight is dramatic.
The numbers can also look different from what Windows Task Manager shows. When you close a tab, Chrome hands the memory back but the operating system may hold onto it for a while in case another process needs it. The browser’s own task manager gives the more accurate picture of what your tabs are actually using right now.
That shortcut — Shift + Esc — is worth committing to memory. Most browser slowdowns are not mysteries. They’re one greedy tab or one forgotten extension, and now you know exactly where they’re listed.
More browser-side fixes live in our Apps & Software section.
