3 ms·

not gp, but 1 - crashes, approximately bimonthly. Chrome just doesn't crash for me any more. 2 - very high cpu usage if ff runs long enough. Eventually it w

by x0x0 10y ago

not gp, but 1 - crashes, approximately bimonthly. Chrome just doesn't crash for me any more. 2 - very high cpu usage if ff runs long enough. Eventually it will creep up towards consuming 50%+ of a cpu 3 - similar problems with memory usage. Chrome is a pig, but if you close windows, the system gets memory back. FF just doesn't seem to return memory to the system w/o a full restart. 4 - intermittent freezes when loading new tabs. The entire app becomes unresponsive, long enough to notice / feel jerky. fwiw, I leave chrome up for weeks on end and don't have these issues. osx 10.9

kyllo 10y ago
I also get window rendering issues in FF on Windows 10 after waking my laptop from sleep. The browser can still be used but the frame goes totally white. Very weird.
- frik 10y ago
  I get rendering issues after waking the notebook from sleep in Win7 as well. Also I get rendering issues in a Remote Desktop session. If the PC is running for days Firefox crashes automatically after some days. Firefox crashes (whole browser) more often than other browsers. It's annoying that the multi process implementation that so many years to implement and will still break plugin compatibility.
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 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 ago
    Is it a Firefox thing or a Google thing?
  - Drdrdrq 10y ago
    Well, 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 ago
      But 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?
progval 10y ago
Hopefully, Electrolysis will fix 3 and 4. https://wiki.mozilla.org/Electrolysis https://wiki.mozilla.org/Electrolysis

by x0x0 10y ago

kyllo 10y ago

I also get window rendering issues in FF on Windows 10 after waking my laptop from sleep. The browser can still be used but the frame goes totally white. Very weird.

frik 10y ago
I get rendering issues after waking the notebook from sleep in Win7 as well. Also I get rendering issues in a Remote Desktop session. If the PC is running for days Firefox crashes automatically after some days. Firefox crashes (whole browser) more often than other browsers. It's annoying that the multi process implementation that so many years to implement and will still break plugin compatibility.

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 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 ago
  Is it a Firefox thing or a Google thing?
- Drdrdrq 10y ago
  Well, 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 ago
    But 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?

progval 10y ago

Hopefully, Electrolysis will fix 3 and 4. https://wiki.mozilla.org/Electrolysis https://wiki.mozilla.org/Electrolysis