One thing I noticed and I am pretty sure a lot of others must have had is, while chrome is running if you check the windows task manager you can see quiet a few processes running with the name chrome. My first reaction was, WOW, smart startegy from google. So this is the way they prevent the browser from crashing even if a single tab crashes. From what I have understood and have convinced myself to be the fact is, that each tab in crome runs as a separate process. Now this has a lot of obvious and not so obvious advantages.
a) As stated earlier each tab is a separate process and hence it crashing of one tab dowsn't affect the browser itself.
b) With each process having itz own memory footprint and being independent of other, one chrome process getting slow or getting stuck doesn't affect teh other. So a person will never notice the browser getting slo though there might be a few tabs that might be using a lot of memory and being not responsive. This is all my interpretation of multiple chrome processes running. I am not sure if it is true or not.
c) Now considering that I am right, it means the amount of memory used by chrome will keep increasing with the number of tabs, which is true for firefox too. So ultimately firefox and chrome will show similar results when stree tested.
d)One nice feature of chrome that I noticed today is, in case the page is not available any more in the current location, chrome offers you to see the last cached shot of the page as taken by google.
I am still not sure if the multiple processes represent no of tabs open in chrome, but there is s.th the way google is handling the load on chrome by using separate processes.
Thats it for now. Will keep posting in case I am able to find s.th new.
No comments:
Post a Comment