moving parts (scrolling etc.) stutter above 60 hz monitor refresh rate
Categories
(Core :: Graphics, defect, P3)
Tracking
()
People
(Reporter: barb.bugzilla, Unassigned)
Details
Attachments
(1 file)
45.95 KB,
text/plain
|
Details |
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:79.0) Gecko/20100101 Firefox/79.0
Steps to reproduce:
Use a monitor with a refresh rate higher than 60 Hz (in my case 75 Hz).
When scrolling you'll notice a stutter. I already looked for many possible solutions in the internet, including disabling and enabling various variables in about:config, in the nvidia control panel or played with my monitor's settings.
I have a monitor that allows a refresh rate up to 75 Hz. I found out that the stutter is gone when I limit the refresh rate to 60 in windows settings.
It's even worse when I play a game. The stutter while scrolling is really annoying. Again, all of this stutter is completely gone after I set the rate to 60 Hz.
Actual results:
Scrolling or moving parts stutter when refresh rate is higher than 60 Hz. Example site where you can test it: https://testufo.com/stutter#test=stutter&demo=smooth
Expected results:
No stutter
Comment 1•4 years ago
|
||
Reproduced on the latest versions of Firefox Nightly 81.0a1 (2020-08-09), beta 80.0b6 and release 79.0 using the provided steps and website.
Setting a component for this issue in order to get the dev team involved.
If you feel it's an incorrect one please feel free to change it to a more appropriate one.
Comment 2•4 years ago
|
||
@Barb: Could you attach your "about:support" information (navigate to it in the url bar).
Updated•4 years ago
|
Reporter | ||
Comment 3•4 years ago
|
||
Reporter | ||
Comment 4•4 years ago
|
||
(In reply to Kris Taeleman (:ktaeleman) from comment #2)
@Barb: Could you attach your "about:support" information (navigate to it in the url bar).
Added an attachement, I hope this is what you wanted and I didn't leak my credit card number with that :P..
Joking aside, I already did the usual steps, like reinstalling Firefox, fresh installing firefox, jumping 3 times and whispering 'fix yourself, Firefox, I believe in you', but it all didn't work.
To get that attachment I changed my refresh rate to 75 Hz again and it instantly is stuttering while scrolling again. 60 Hz resolves all issues.
Comment 5•4 years ago
•
|
||
@Barb: Thanks for the system info!
It seems like when going higher than 60Hz, our new render backend gets disabled which is why you might see performance issues on top of some potential high refresh rate.
Comment 6•4 years ago
|
||
Sorry, wanted to ask more info, but noticed the reason why it picked the slower backend.
You could try forcing webrender on, it might work at 75Hz. To enable webrender: go to 'about:config', search for gfx.webrender.all, set that to true and restart the browser.
@Andrew: Do you know what the outstanding work for higher refresh rate monitors is? It gets disabled here: https://searchfox.org/mozilla-central/source/gfx/config/gfxConfigManager.cpp#185
Reporter | ||
Comment 7•4 years ago
|
||
(In reply to Kris Taeleman (:ktaeleman) from comment #6)
Sorry, wanted to ask more info, but noticed the reason why it picked the slower backend.
You could try forcing webrender on, it might work at 75Hz. To enable webrender: go to 'about:config', search for gfx.webrender.all, set that to true and restart the browser.@Andrew: Do you know what the outstanding work for higher refresh rate monitors is? It gets disabled here: https://searchfox.org/mozilla-central/source/gfx/config/gfxConfigManager.cpp#185
Thanks a lot, setting that setting to true actually fixed it! I thought I already had tried all options and toggles but apparently I did not. Thanks again, you are awesome!
Updated•3 years ago
|
Comment 8•2 years ago
|
||
Can change gfx.webrender.all back to the default and see if the problem comes back?
Updated•2 years ago
|
Reporter | ||
Comment 9•2 years ago
|
||
(In reply to Jeff Muizelaar [:jrmuizel] from comment #8)
Can change gfx.webrender.all back to the default and see if the problem comes back?
I don't know anymore if I did it myself or if some update did it, but the setting already is back to the default and the problem doesn't occur anymore.
Updated•2 years ago
|
Description
•