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.
Thread beginning with comment 329404
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:
2006-01-02
From reading their development website, one of the reasons they went with the option of operating in the single-process model was because it's easier to debug using the standard Visual Studio debugging environment. Once they had the feature, what's the point of suffering the pain of removing it, especially since they expect some of the users to also work on developing Chrome's open source codebase?
[Posted from Chrome, on which I just seem to have hit a scrolling bug]