If you look in Windows Task Manager, it’s quite difficult to tell which tab in Chrome is chewing up all that memory. How can you easily tell which tab is associated with which process?

Today’s Question & Answer session comes to us courtesy of SuperUser—a subdivision of Stack Exchange, a community-driven grouping of Q&A web sites.

The Question

SuperUser reader KCArpe wants to know how he can see which Chrome tab is using what system resources:

How do I identify which process belongs to which tab in Google Chrome?

Normally, I have a (ridiculously) large number of tabs open. If I need to free memory on my box, I would like to choose based on tab/process memory footprint.

Since looking in Task Manager just yields dozens of identical chrome.exe entries, how can he tell?

The Answers

SuperUser contributor Dennis writes:

In chrome://memory-redirect/, you can see all open processes (tabs, plugins, extensions, etc.), including their private memory usage and their PID.

Using the PID, you can kill the corresponding process from a Command Prompt / Terminal:

Windows: taskkill /PID <PID>

Linux: kill <PID>

Contributor Dracs adds in another way to take a peek at the processes:

Chrome has it’s own in-built task manager which makes it easy to identify which process belongs to which tab(s). You can access it by the hotkey Shift+Esc or by right clicking on the title bar and selecting “Task Manager”.

Chrome also has a more detailed memory page which can be accessed by opening a new tab and entering chrome://memory-redirect/ into the omnibox. It can also be accessed via the “Stats for nerds” link in the Task Manager.

Have something to add to the explanation? Sound off in the the comments. Want to read more answers from other tech-savvy Stack Exchange users? Check out the full discussion thread here.

Profile Photo for Jason Fitzpatrick Jason Fitzpatrick
Jason Fitzpatrick is the Senior Smart Home Editor at How-To Geek. He has over a decade of experience in publishing and has authored thousands of articles at How-To Geek, Review Geek, LifeSavvy, and Lifehacker. Jason served as Lifehacker's Weekend Editor before he joined How-To Geek.
Read Full Bio »