4 ms·

I'm kind of sick of hearing complaints about Chrome's multiple processes being somehow a bad thing. You want fewer processes in Chrome, then you go on to compla

I'm kind of sick of hearing complaints about Chrome's multiple processes being somehow a bad thing. You want fewer processes in Chrome, then you go on to complain about Firefox's crashed tabs. Do you understand that's one of the benefits of having multiple processes? If one process crashes, it very rarely effects the performance of any other processes. It's not keeping all of your eggs in one basket. It provides better security as well. So I'm at a loss as to why so few people can appreciate it. Considering these benefits, memory usage is totally reasonable.

frik 11y ago
Are you answering my comment? You wrote your own unrelated rant. I only wrote about it would be great if you could configure Chrome's process spawning logic. IE does it in an more intelligent way to consume less memory by spawning a bit less processes (a trade off, as if one tab crashes more tabs have to be reloaded). But giving a power user (who have 100+ tabs open) a choice would be great.