Arch Linux

dimich

Member

From: Kharkiv, Ukraine

Registered: 2009-11-03

Posts: 598

[SOLVED] Firefox high CPU load with google search results tab active

I started noticing Firefox process sometimes heavily loads CPU (about 350-400% according to top, i5-8365U with 4 cores, 8 thread). Not sure when it started to happen, maybe two weeks or month ago.
For now it is observed only when tab with google search results page is active. If I switch to another tab, CPU load drops to 1-5% immediately.
Tried to turn off add-ons (Adblock Plus, NoScript, despite they are already disabled for google.com domain) - the heavy load remains.
This doesn't always happen: sometimes search results page may stay active for a long time without significant CPU load. If I close Firefox and start it again restoring previous state with the same active tab, likely it won't reproduce.
Tried with fresh profile and not logged into google's account, with the same search prompt - doesn't seem to reproduce, no heavy load observed.
Tried to debug with built-in Firefox profiler (about:processes -> Profile all threads... for main process) but I don't know what to pay attention to and how to interpret results.
Firefox-150.0.1-1.
Does anyone observe the same behavior? I'd appreciate for suggestions how to fix it or investigate it further.

Last edited by dimich (Yesterday 07:58:55)

seth

Member

From: Won't reply 2 private help req

Registered: 2012-09-03

Posts: 75,204

Re: [SOLVED] Firefox high CPU load with google search results tab active

Do you get this when turning off the AI results, "&udm=14" ?

---

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

dimich

Member

From: Kharkiv, Ukraine

Registered: 2009-11-03

Posts: 598

Re: [SOLVED] Firefox high CPU load with google search results tab active

Do you get this when turning off the AI results, "&udm=14" ?

Indeed, high CPU load doesn't seem to reproduce with AI overview turned off. Thank you!
Further search in this direction led to https://www.reddit.com/r/firefox/commen … cpu_usage/ and https://bugzilla.mozilla.org/show_bug.cgi?id=2033282.
Blocking

www.gstatic.com/searchbox-team/eclipse_wave_blurred

seems to solve the issue, at least for now.