4 ms·
It's odd to see Firefox being called a memory hog just a few years back. As far as I can tell, Chrome has used more memory pretty much always if you have multip
by 8xde0wcNwpslOw 9y ago
It's odd to see Firefox being called a memory hog just a few years back. As far as I can tell, Chrome has used more memory pretty much always if you have multiple tabs open.
(Firefox may have been slower on slow hardware, but that has never been an issue for me.)
- kylek 9y agoI really wish https://areweslimyet.com/ https://areweslimyet.com/ was still updated (and more comprehensive, ala https://arewefastyet.com/ https://arewefastyet.com/).
- com2kid 9y agoFF was still 32bit and without per process tabs it would run out of memory and crash multiple times a day for heavy users. With multiple processes and being 64bit across all platforms, those particular complaints are gone.
- newscracker 9y agoI'd probably be saying this for the hundredth time or whatever, but I've always seen the machine crawl after Chrome opens a few tens of tabs and uses a lot of memory, while Firefox (even before Quantum) would use a lot lesser memory for the same number of tabs. Firefox has always been my browser whenever I need(ed) to have several tens of tabs open. The extensions in Firefox also have worked much better for me, all along. Even today, Chrome wouldn't restore tabs after crashing and relaunching, and this was after it asked me if I would like to restore tabs and I said yes. Chrome, to me, is nothing but a toy browser good for some single tabbed kiosks or a open-read-close model of use. For anyone who wants a browser for heavy use, especially with a lot of tabs, I would recommend only Firefox.