This thread was archived. Please ask a new question if you need help.
FF uses 100+ CPU on my otherwise totally fast up-to-date MacBook. This, despite doing all the fixes suggested, repeatedly.
It has gotten so bad that it constantly overheats my Mac, causes my fan to go on full blast non-stop, even when it's in the background, so I basically have to stop using it.
Mozilla needs to get serious and overhaul this heavy-use browser.
When they can. Many other users also need help.Read this answer in context 👍 0
All Replies (5)
Has a bug been filed in https://bugzilla.mozilla.org/ on this issue? If so, please post the bug number as I'd like to follow it.
(I also had this problem and finally upgraded the memory in my MBP from 4GB to 8GB. FF is still a memory pig, but at least now when it is consuming 2.61GB of real memory and has kernel_task up to 2.84GB it doesn't give me the beachball as much or for as long.)
I've got 12GB of RAM, which allows it to work longer than if I only had 4 or even 8, but it's still a royal pain...
Last reply by StephenCee - ONE MONTH AGO! This apparently very common problem which totally makes using FF a chore is obviously of little importance to Mozilla Support. I have put up with this for ages, and now have finally given up to try Internet Explorer (that's how fed up and desperate I am!), its replacement, or Chrome - or anything else that will let me actually work on the web without burning out fan bearings or having to stop work and have dinner before returning to see if FF is yet in a usable state - ie. where links are clickable, mouse wheel actually rolls screen, and something bloody works!
Modified by Kuib
Unfortunately, I have given up and now have had to use Chrome as my default browser, much as I hate Google.
Every time I do go back and try to use FF, after updating, I still get issues, and also a lot of getting stuck, jumping, etc.
Fortunately, a lot of the extensions developers make the same basic extensions for Chrome as they do FF.
I really believe in what FF and Mozilla is supposed to be all about, just dont' get the consistent denial of this issue.
seeclear, I agree with you completely. So sorry to have to ditch FF but see no other option until resource probs are sorted. Chrome here I come...