4 ms·
The burning of CPU cycles whilst idling on Google's result page is the most infuriating bug in Firefox but doesn't seem to have been accorded any priority. It
by dingaling 10y ago
The burning of CPU cycles whilst idling on Google's result page is the most infuriating bug in Firefox but doesn't seem to have been accorded any priority. It has persisted for at least three years.
https://support.mozilla.org/fr/questions/965360 https://support.mozilla.org/fr/questions/965360
Unfortunately I usually only remember to close the results tabs when my fan spins-up.
- eitland 10y agoIs it a Firefox thing or a Google thing?
- Drdrdrq 10y agoWell, you could always just use startpage.com (uses Google) or duckduckgo.com. It's not like Google is still ages ahead of the competition as it once was. I am not sure where the bug comes from but it would be much easier for Google to fix it, given that their JS is heavily obfuscated. But then again, that's not really in their interest, is it?
- eitland 10y agoBut then again, that's not really in their interest, is it? That thought struck me as well. Lets ask :-) Googlers at HN: is this a lack of QA, a deliberate stab at Firefox or something else?