4 ms·
Just as an aside, the reason Chrome is using so much memory is that each tab runs in its own process. This affords some security and stability benefits (one pro
by kintamanimatt 13y ago
Just as an aside, the reason Chrome is using so much memory is that each tab runs in its own process. This affords some security and stability benefits (one process dies, the rest are fine), but it obviously comes with a major price. I see this as a major architectural flaw in Chrome.
- ygra 13y agoChrome did this since the beginning but didn't use that much memory back then. So clearly processes aren't the only answer.
- kintamanimatt 13y agoChrome's codebase also got more complex so now every new process consumes a lot more memory. It's a way of achieving concurrency, but it's not necessarily the best way in terms of memory footprint.
- venomsnake 13y agoI think the processes are not the main culprit. We are using way more massive DOMs and a lot of js these days. And there hasn't been solid memory optimization efforts for js VMsas far as I know. The focus was purely on speed the last few years.
- kintamanimatt 13y agoI'm under the impression there was for SpiderMonkey, but I haven't followed it very closely. [0] [0] http://blog.mozilla.org/nnethercote/2011/11/01/spidermonkey-is-on-a-diet/ http://blog.mozilla.org/nnethercote/2011/11/01/spidermonkey-...