3 ms·
1. Know the problem but for me it is infrequent enough and the bandaid (restore last session) is good enough that I don't care. 2. Painful for me as well unti
by eitland 10y ago
1. Know the problem but for me it is infrequent enough and the bandaid (restore last session) is good enough that I don't care.
2. Painful for me as well until I I blocked js in google search and search results. (I often have quite a number of tab trees open and the roots are often google search results and they eat CPU if not restrained. I don't know if this is intentional on googles part but it leadt it shows poor attention to QA.)
Just recently learned about about:performance and it is really nice.
- dingaling 10y agoThe 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?