Friday, September 05, 2008

chrome is not one process per tab

As you can read on several places all over the internet, chrome is the new internet browser from google. I would be silly not to take a look into this new beauty, so i did. I did liked it, and sure i will use it now and then for different sites, however it is not going to be my default browser, even with his cool look and feel.(basically I agree with this post by anima9 )

Anyhow I wanted to correct some misunderstanding related to chrome tab isolation: Word is out that one of its key features is that it uses a separate process per tab, but chrome it self can show you this is not true. Chrome ships with a nice Task Manager, and it can show you this, however, more interesting is the about:memory page (you will have to type this since it takes you to "about:blank"). There you can see how some related tabs may "live" under the same PID.

This is what surprised me: It joins four tabs under PID 7696.

How are these tabs related?, well, my guess is those have been open via "open in new tab", but that is just my guess, and i'm not going to dive into the source code to find out.

2 comments:

Anonymous said...

It doesn't matter as long as it uses a separate thread for each tab and handles thread exceptions properly.

Anonymous said...

See http://www.google.com/chrome/intl/en/webmasters-faq.html

"Google Chrome has a multi-process architecture, meaning tabs can run in separate processes from each other, and from the main browser process. New tabs spawned from a web page, however, are usually opened in the same process, so that the original page can access the new tab using JavaScript."