16 December, 2012

by Updated on 16 December, 2012 Leave a Comment

Find & Kill Problematic Chrome Extensions, Processes, Tabs Which Uses More Memory

Google Chrome handles each tab separately and also monitors every extension and plugin process separately. This makes the browser more stable and does not affect the performance if one tab or extension or an add-on freezes.If you see multiple chrome processes but only one tab open, other processes are for extensions. We do not use all the extensions that we have installed. Some extensions and plugins keep using system resources even if we are not using them at all.
Some web pages also uses more memory and processing power. It is always better to kill those processes which causes problem to Chrome performance.

You can easily find and kill every tab, extension, add on or any other browser process and sort them on the basis of memory usage and processor usage.

view-chrome-background-process
  • To find out, go to Google Chrome menu and select "View background pages' option.
kill-chrome-extension-freezing
  • The task column lists all the installed and enabled extensions as well as all open tabs, processes and add-ons currently using system resources and interacting with the browser.
  • You can sort the processes by clicking the heading of the column. Select the process you want to kill and click on the buttons 'End Process'
  • It will kill the process. When you kill the process, a notification will be displayed.
  • You can also use this task manager to find you the page loading speed, just reload the open tab or open a new tab and see the network column.
This way you can easily close any specific tab that is not responding or an extension that is creating problem or also a flash add-on that is not running properly.

Do you have any other method to kill the processes and keep your favorite browser running? Please share with me.

About The Author
Passionate Technology Blogger. Not a profession. Find only real life useful and simplified Tech articles, How-To's on TopTrix.

0 comments:

Post a Comment