title: Why is the 'Google Chrome Renderer' multi-processes, not multi-threaded?
body: <p>Every time I load a browser tag in Chrome on my mac, the application forks another process. This seems to be different from how firefox or Safari work. What was the reason why Google stayed away from multi-threading in this case? The problem to be solved here (rendering multiple pages at once would seem in my mind to be a prime candidate for muti-threading, or?</p>