Re:Revisiting how we build Firefox
by chuckharmston on Monday July 06, 2015 @08:17PM
(#9842924)
Firefox itself is quite fast [1]; if you're having issues, there's a good chance that it's due to an add-on [2]. A (historically; I'm unsure if this is still the case) particularly egregious offender [3] is AdBlock Plus, but µBlock [4] does come highly recommended.
[2] https://support.mozilla.org/en-US/kb/firefox-uses-too-much-m...
[3] https://blog.mozilla.org/nnethercote/2014/05/14/adblock-plus...
I didn't say it slow. It is indeed fast.
Thank you for that!
Until suddenly the show stops and I have to kill it via Taskmgr to inject new life into it due to memory suffocation.
Re:Revisiting how we build Firefox
by chuckharmston on Monday July 06, 2015 @08:25PM
(#9842942)
Hmm...that doesn't sound like normal behavior; my uneducated guess would be that there's a specific webpage or extension with a leak. Next time it happens, it'd be fantastic if you could go to about:memory, save the reports, and file a bug with them attached:
Firefox is not a bloated memory hog (anymore).
I'll send you a memory consumption snapshot soon.
8 tabs == 1GB memory already but i can live with it for now.
When it eats 3GB+ -- and unfortunately it will - then it'll become an issue.
Do you have unusual plugins that might be using a lot of RAM? Do the same tabs take up less memory in Chrome?
Do not make tabs cuter, I don't care about it.
But PLEASE - do something to stop Firefox from being such a bloated memory hog - I deeply care about it.