4 ms·
Firefox is actually much less resource-hungry than Chrome, though that's largely because it doesn't (yet) use different processes for different tabs....
by scholia 12y ago
Firefox is actually much less resource-hungry than Chrome, though that's largely because it doesn't (yet) use different processes for different tabs....
- cbsmith 12y agoActually, you can turn that on now to check it out: http://www.jkwebtalks.com/2014/02/enable-multi-process-tabs-in-firefox.html http://www.jkwebtalks.com/2014/02/enable-multi-process-tabs-...
- Dylan16807 12y agoNo, that uses a single process for all tabs.
- cbsmith 12y ago? No, the multi-process tab feature is all about one process per tab.
- Dylan16807 12y agoMaybe someday. Not today. You get one tab process that crashes often. And I wouldn't say that's the 'point'. Chrome groups tabs into fewer processes most of the time. Personally I'm much more excited about the possibility of a compacting GC.
- scholia 12y agoYou get one process that crashes about as often as Chrome, though it consumes fewer resources and is much faster to restart (by not loading tabs unless you go to them). The increasing crashiness of Chrome was one of the reasons I stopped using it.
- Dylan16807 12y agoYou're a lot luckier than I am. Also it still takes a nontrivial amount of time to not-load a lot of tabs.
- scholia 12y agoNot-loading tabs is a heck of a lot quicker than loading them (and I usually have more than 500 in Firefox). Otherwise, I'm not the only person who has had too many problems with Chrome: https://productforums.google.com/forum/?utm_medium=email&utm_source=footer#!topic/chrome/FwgIERQmHxg[1-25-false] https://productforums.google.com/forum/?utm_medium=email&utm...