When using nVidia GPU, firefox scroll lags
Categories
(Core :: Graphics, defect, P3)
Tracking
()
People
(Reporter: mystiquewolf, Unassigned)
Details
Attachments
(3 files)
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:67.0) Gecko/20100101 Firefox/67.0
Steps to reproduce:
- Use nVidia GPU (nVidia GeForce MX150) with Firefox 67.0b4
- Open some pages
- Scroll down a bit, stop, scroll down again a bit.
Actual results:
The page doesn't start scrolling smoothly, it jumps a little bit down and only then starts scrolling smoothly. Not happening with integrated Intel UHD 620 GPU.
Expected results:
This bug is happening since many months. I used to use Intel GPU for Firefox as it still doesn't lag videos on it but also scrolling is smoother. Only reason i selected Nvidia for Firefox is i want to test WebRender.
However, no matter if WebRender is enabled or not, since many months this bug exists. Guys and ladies, please take some action now. How can i help with info for fixing this? Tests, data, etc. Let's fix it. I always update GPU drivers with latest via GeForce experience app.
Reporter | ||
Comment 1•5 years ago
|
||
Some screencasts:
https://www.youtube.com/watch?v=5rz79F30aLU&feature=youtu.be
https://www.youtube.com/watch?v=WLEd3GmJleY&feature=youtu.be
Although i also update Windows (or better said it updates whenever it likes :)), it reproduces on latest Windows 10 v1809 build 17763.379 and in all of the last 10 months or so. Maybe since i got the PC and tried the first time with Nvidia. Who knows from when does this appear!?!?!
Updated•5 years ago
|
Comment 2•5 years ago
|
||
Can you confirm that the same problem happens with WebRender disabled?
Reporter | ||
Comment 3•5 years ago
|
||
Yes, i can confirm. It appears on stable and i don't know since when. I think 4-5 months ago it was the same.
Reporter | ||
Comment 4•5 years ago
|
||
I believe it happens when i leave the site for about 5-10 seconds without scrolling, then the next scroll has this initial lag.
Updated•5 years ago
|
Comment 5•5 years ago
|
||
(In reply to Lyubomir Parvanov from comment #4)
I believe it happens when i leave the site for about 5-10 seconds without scrolling, then the next scroll has this initial lag.
If you go to about:config and change apz.displayport_expiry_ms upwards (say to 60000 from the default of 15000) does that help? I suspect with that change you will need to leave the site for a whole minute without scrolling before the next scroll has the lag. Can you confirm that?
Reporter | ||
Comment 6•5 years ago
|
||
I changed it, then restarted the browser, but saw no change. It was still taking about the same time for the lags to appear. Also why does it appear only when nVidia is the GPU for Firefox?
It seems like it never appears when i switch from another tab, the one that was switched to scrolls okay. If i scroll and leave it for a little time it appears.
Reporter | ||
Comment 7•5 years ago
|
||
Nvidia settings for Firefox. I'm using balanced profile and it cascades from global settings.
Reporter | ||
Comment 8•5 years ago
|
||
Reporter | ||
Comment 9•5 years ago
|
||
Reporter | ||
Comment 10•5 years ago
|
||
Scroll issues also happen when reading PDFs.
Comment 11•5 years ago
|
||
Ok, thanks. In that case getting a Gecko profile (see instructions) might help. Probably best to do it with WebRender disabled since then the default thread selection should have all the relevant information. If you enable WebRender you'll want to also enable the "Renderer" and "RenderBackend" threads in the profiler add-on settings before starting the profiler.
Reporter | ||
Comment 12•5 years ago
|
||
Here are captures. I pressed Ctrl+Shift+2 as soon as i could after the issue appeared.
Comment 13•5 years ago
|
||
The jank is likely caused by the hundreds of milliseconds spent in DXGI AcquireSync.
Comment 14•5 years ago
|
||
Can you try disabling Direct2D by setting gfx.direct2d.disabled to true?
Reporter | ||
Comment 15•5 years ago
|
||
Disabled it, but the issue still occurs. :-/
Updated•5 years ago
|
Updated•5 years ago
|
Reporter | ||
Comment 16•5 years ago
|
||
I guess this has something to do with #1383563, as it's the exact same symptoms.
Updated•2 years ago
|
Description
•