Most of us are used to the Windows Task Manager ( Ctrl + Alt + Delete ) feature in Windows but did you know there is something similar specifically for Chrome? (Neither did I, Shame on me).
There are a few situations that the Chrome Task manager can be handy – for example, if you noticed that Chrome has become a bit sluggish or a specific tab has become unresponsive.
You can also use it to check out which Chrome extension is memory intensive and disable that particular plug-in to have a better surfing experience.
Using the Chrome Task Manager
In order to open the Chrome task manager, open the Chrome browser, and right-click on your tab bar at the top and select task manager.
If you prefer keyboard shortcuts, you can press: Shift + Esc to access it.
Chrome task manager
In the new window, you will see a list of opened tabs and plugins actively running along with their corresponding memory usage. Select the one (you can also select multiple at once) you had like to terminate and click End Process.
If you had like to access even more memory information, you can click on the Stats for nerds option. You will then see a detailed memory usage about each opened tabs in Chrome and also memory consumed by other browser vendors.
For example, I have opened Chrome, Firefox, and Safari. Under Summary, you can see the memory usage for each browser.
Chrome Task Manager- Stats for nerds
Firefox task manager, Unfortunately, there is no such feature shipped natively in Firefox. The good news is that there is a nice little plugin I have been using lately that does provide you memory usage statistics.
However, you can’t get other details that Chrome task manager gives you, like CPU and network usage, process ids, etc.
If you had like to check it out, you may download about:addons-memory extension. You will get a nice-looking report with how much memory is being consumed by each of your extensions. Firefox Task manager
There is also the about memory page (type this in your address bar) that will give you a very technical view of how Firefox is using the memory. You should be careful though if you are unsure what you are doing.