http://mattsblog.ca/2008/09/04/google-chrome-tab-processes/ Tue, 06 Jul 2010 20:36:08 +0000 hourly 1 http://wordpress.org/?v=3.0-beta2-15006 http://mattsblog.ca/2008/09/04/google-chrome-tab-processes/#comment-20904 Google Chrome, is it Just Another Web Browser? « Matt's Blog Mon, 08 Sep 2008 02:17:38 +0000 http://mattsblog.ca/?p=534#comment-20904 [...] Interestingly, Chrome is also very unlikely to crash or become unresponsive. This is because each tab is given its own separate process (so if you have multiple tabs open, you’ll see multiple instances of “chrome.exe” in your Windows Task Manager), meaning that when a site in one tab is unstable, it may cause that tab to become unresponsive and crash, but the rest of your tabs will remain responsive and in perfect working order. This actually does work, I went to a site that used Shockwave, then the Shockwave Player crashed and the tab became unresponsive, however the rest of Chrome was perfectly fine. Chrome will then actually tell you why the tab became unresponsive (or crashed). This has already proved to be much more convienant than the whole browser crashing and then restarting (Mozilla and Microsoft should take note of this). However, there is one problem with this, when you’re in the Task Manager, there is no way to tell which chrome.exe process is associated with what tab. So, if there’s a process that’s using a large amount of resources, there’s no way to know which tab to close down. Hopefully they’ll be able to fix this by adding the tab name to the description of the process, or with some similar solution. UPDATE: There actually is a way to tell which process is which, see my post on it here. [...] [...] Interestingly, Chrome is also very unlikely to crash or become unresponsive. This is because each tab is given its own separate process (so if you have multiple tabs open, you’ll see multiple instances of “chrome.exe” in your Windows Task Manager), meaning that when a site in one tab is unstable, it may cause that tab to become unresponsive and crash, but the rest of your tabs will remain responsive and in perfect working order. This actually does work, I went to a site that used Shockwave, then the Shockwave Player crashed and the tab became unresponsive, however the rest of Chrome was perfectly fine. Chrome will then actually tell you why the tab became unresponsive (or crashed). This has already proved to be much more convienant than the whole browser crashing and then restarting (Mozilla and Microsoft should take note of this). However, there is one problem with this, when you’re in the Task Manager, there is no way to tell which chrome.exe process is associated with what tab. So, if there’s a process that’s using a large amount of resources, there’s no way to know which tab to close down. Hopefully they’ll be able to fix this by adding the tab name to the description of the process, or with some similar solution. UPDATE: There actually is a way to tell which process is which, see my post on it here. [...]

]]>