Upcoming Firefox 57 ("Quantum") is twice as fast as Firefox 52

Having some oddities with rendering with 60 - its like after awhile certain page elements on a tab that you've loaded up but not switched to for a few minutes are "hibernated" and slow to load back in after switching back to that tab - sometimes showing random text or images from other elements for a moment before the correct data is "paged" in.
 
a google does not reveal it has an auto tab unload in native firefox yet
- the great discarder add on I use in chrome suppresses it's voracious memory habit.
 
jpaul said:
a google does not reveal it has an auto tab unload in native firefox yet
- the great discarder add on I use in chrome suppresses it's voracious memory habit.
Click to expand...

Seems to be related to certain websites, Facebook being one of them, in 60.
 
Dunno if it was a one off but first time running FF after updating to 60.0.1 hard locked my machine the moment the UI appeared before populating it with anything graphical with an eventual driver recovery :( never normally have any issues. Nothing in event log, etc. so no idea WTF happened.
 
Rroff said:
Dunno if it was a one off but first time running FF after updating to 60.0.1 hard locked my machine the moment the UI appeared before populating it with anything graphical with an eventual driver recovery :( never normally have any issues. Nothing in event log, etc. so no idea WTF happened.
Click to expand...

Just updated and no problems here.
 
Kelt said:
Just updated and no problems here.
Click to expand...

So far not happened again. I've had the same thing happen on a couple of other systems that also aren't on the latest nVidia drivers - not always immediately on first run but fairly shortly after updating but so far then hasn't happened again, the systems with latest drivers so far haven't exhibited it. Wonder if its some incidental fallout from changes related to the ongoing TDR issues with FF and nVidia drivers (none of these systems have ever had issues with that).

EDIT: Looks like it isn't FF that is the problem, not 100% sure yet but think it was another piece of software I updated at the same time.

EDIT2: 99% it was another piece of software updating that is the problem but it is hard to narrow down for sure :( either that or 3 of my GPUs have become borderline unstable all within a few hours of each other. At this point I'm fairly sure FF is just collateral.
 
Last edited:
60.0.0.1 Is using massive amounts of RAM on my machine and the tabs are laggy and unresponsive.
I had 2 tabs open on FF and it was using over 3Gb of RAM, I also had the exact same tabs open in Chrome and it was under half the amount of FF.
It started happening with 60.0 but has been more recently. Google maps and geoguessr make it happen lots but it can happen on any site. I just went on Facebook to message a shop and it went all laggy and I could not even highlight text or scroll.
I have gone back to Chrome for the time being which is a shame.
I did not have high CPU usage just the odd spike. Hope they fix it soon.
 
I've been having some issues as well now with the GPU drivers and FF.

Only yesterday twice, the browser freezes the screen goes black and then refreshes.

No driver crashes but it's the GPU acceleration having issues.

All good today tho.
 
I am not convinced the GPU acceleration helps much with a 4core I7 anyway - afaik they have not yet added the new webrender into ff.
- reposting earlier link https://hacks.mozilla.org/2017/10/the-whole-web-at-maximum-fps-how-webrender-gets-rid-of-jank/

Simps said:
Google maps and geoguessr make it happen lots but it can happen on any site
Click to expand...
google maps is the biggest resource hog (pile of junk) out there no ?- fan inaviably go's on if I use it ... so I use here maps unless I need a streetview.
I think it must be caching masses of map segments/pictures in anticipation that they are needed
 
I know that about gmaps but it never happened before the 60.0 update on google maps.
It also happens on other sites, the screen will go grey and you get a black circle spinning in the middle of the screen. You can close that tab and the other tabs are unaffected.
Maybe it happens on google maps more because as you say the amount of resources it requires.
 
Only since FF 60 have I started having GPU acceleration issues. Probably doesn't help I am using an old AMD 6450 so drivers are from 2015 I think.

Happening quite a lot today.
 
Last edited:
This is confusing rolled back to 60.0 on the machines that have been having problems and no more issues - but the problem doesn't always happen when FF is actually running which a long with a number of other programs updating I thought meant it was some other software or somehow 3 of my GPUs all decided to go faulty at the same time... but now I've put FF back a version so far no more problems...
 
Can't figure this one out - unless nVidia have some driver level "hacks" that are in effect if it even detects certain (versions of) applications installed not even running.

On several, but not every, system I have FF on if I update to 6.0.1 if I just boot them up and do nothing, as far as I can see nothing FF is related is even running, they encounter a 116 BSOD within an hour, definitely within 2 hours. If I'm actually using them they will randomly just black screen with the monitor losing signal and/or nVidia driver time out and recovery but only when either starting FF or when clicking on a link, etc. not just while the browser is idle or semi-idle on the same page(s).

Reinstall 60.0 and I can leave them fine for hours with no problems so not like the GPUs are dying, etc.
 
According to this all the browsers are losing out to Chrome which sits at 62.8%.

You would think with all this privacy backlash which has been going on recently people would wise up and avoid it and go with alternatives but apparently not.
 
You must log in or register to reply here.
Back
Top Bottom