v154 problem - high cpu, v153 - all good
First post. Not really a question.
I noticed last week that some pages didn't load, and Activity monitor showing Firefox app using 170-180% which I know is way too high. Forgot to check memory usage.
I rolled back from 154 to 153 by restoring it from backup, and same with the Firefox folder in ~lib/appsupp/, relaunched Firefox and cpu was back to 2-4% cpu with a couple of windows and tabs. I've turned off auto-updates.
On my system, something is wrong with v154.
Mac Mini M4 Pro 12-core 24/512, macOS 15.7.5.
All Replies (5)
Good news is v153 also has Extended Support branch, so you can stay on 153 ESR for the year if you're happy with that version.
Thanks for your reply.
What does this Extended Support branch mean? Never heard of it.
I did get a update notification, despite having turned off auto pdates in settings - I just dismissed it.
See Firefox ESR release cycle — it's basically whole year of security support based off of the v153 release branch. Since your current profile data is based on version 153 still, it should be fairly easy to start using ESR and copy over the profile folder, and it should pick up where you left off.
Running mozregression would help identify the culprit that caused the issue.
I spoke too soon. The high cpu problem was still there w/153. When I tried out v153, I failed to open the pages that proved to be triggering the problem, namely streaming live sports in MAX and Viaplay. Some other video streaming sites did not show this behaviour.
Long story short, I quickly found that disabling the Adblock+ extention - poof, problem gone.
Troubleshooting this was fairly quick and easy, as I have many years of experience with music production in DAWs, and there, so-called audio plugins are often the cause of performance problems.
This was with the v4.43.2 of Adblock+, which I believe is the latest.
Anyway, problem seems to be fixed.
You must log in to your account to reply to posts. Please start a new question, if you do not have an account yet.