Linked by Thom Holwerda on Fri 5th Sep 2008 21:57 UTC, submitted by rkalla
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.
Permalink for comment 329433
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
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.