Linked by Thom Holwerda on Fri 5th Sep 2008 21:57 UTC, submitted by rkalla
Google Chrome's process model is extremely sophisticated. The default behavior has been examined before, but you can configure Chrome to manage processes differently: one process per web site, or one process per group of connected tabs, or one process for everything. Marc explains how this all works in Google's new browser. Update: 'Read more' fixed - made a reading comprehension boo-boo there.
Thread beginning with comment 329387
To read all comments associated with this story, please click here.
Read More is Wrong
by TheBashar on Fri 5th Sep 2008 22:25 UTC
TheBashar
Member since:
2005-06-30

Your Read More summary is wrong. According to TFA the default is "--process-per-site-instance". What you describe is the optional "--process-per-site mode".

Reply Score: 1

So?
by kragil on Sat 6th Sep 2008 11:52 in reply to "Read More is Wrong"
kragil Member since:
2006-01-04

Who gives a rats ass?

Google isn't really doing anybody a favor with this browser.

If you look really closely you will see that it is still a beta, but they do _not_ tell you that it has lots of unpatched security flaws and that running a beta has serious implications.

There are active exploits for Chrome and the security and privacy are just horrible. (http://security.bkis.vn/) From the way it is build, installed and preconfigured it just sucks, but people think Google betas are just like other peoples final releases. Gmail is beta for how long now??

Conclusion:

Avoid Chrome.

Reply Parent Score: 3

RE: So?
by Alex Forster on Sat 6th Sep 2008 16:33 in reply to "So?"
Alex Forster Member since:
2005-08-12

I've been watching the Chrome 'vulnerabilities' very intensely. Besides this, there have been ~5 others, all just crashes ("denial of service"). If you'll remember, Safari didn't have too great a launch on Windows, either.

Reply Parent Score: 2