Closed
Bug 1451112
Opened 6 years ago
Closed 4 years ago
Scrolling of specific website very slow with WebRender enabled (http://www.pcgameshardware.de )
Categories
(Core :: Graphics: WebRender, defect, P2)
Tracking
()
RESOLVED
FIXED
People
(Reporter: linuxhippy, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0 Build ID: 20180403100105 Steps to reproduce: 1. Loaded: http://www.pcgameshardware.de/Notebook_Laptop-Hardware-201330/Specials/Ryzen-Mobile-im-Vergleich-1252536/#a3 2. Scrolled down a bit Actual results: When reaching the "blurred" content (paywall), scrolling starts to become choppy with WebRender enabled - while with the default OpenGL compositor it works well. However, I wasn't really able to spot the issue in the profile: https://perfht.ml/2GR7XVS The firefox-bin process consumes 100% cpu, while the GPU profiler shows the GPU is basically idle.
Reporter | ||
Updated•6 years ago
|
Component: Untriaged → Graphics: WebRender
Product: Firefox → Core
Reporter | ||
Comment 1•6 years ago
|
||
some more details about the system: AMD Kaveri 7650k APU, Mesa-17.3.6, Linux-4.15.14
Updated•6 years ago
|
Blocks: stage-wr-trains
Priority: -- → P2
Comment 2•6 years ago
|
||
From the profile it looks like the blob image rendering is blocking the render backend thread, which then blocks APZ hit-testing, which in turn blocks the compositor thread. APZ assumes the RB thread is going to be responsive, so from my point of view the blocking on expensive blob image operations is bad.
Comment 3•6 years ago
|
||
This might actually become a serious problem - Jeff, do we have plans to make blob image rendering not block the render backend thread? If not, and if we can't guarantee a responsive RB thread, then maybe we should go back to using gecko hit-testing rather than using WR hit-testing. Or find a way to do WR hit-testing without blocking on the RB thread.
Flags: needinfo?(jmuizelaar)
Comment 4•6 years ago
|
||
We do have plans to make blob image rendering not block the render backend. See the just filed bug 1455422.
Flags: needinfo?(jmuizelaar)
Comment 6•6 years ago
|
||
Also for the record, I can repro this, and it happens even with async scene building enabled.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 7•6 years ago
|
||
For me this is "better" now in that we don't jank so much, but checkerboard instead. Will leave this open for now since we can probably still improve the perf here. https://perfht.ml/2O7SzFb
Updated•6 years ago
|
Summary: Scrolling of specific website very slow with WebRender enabled → Scrolling of specific website very slow with WebRender enabled (http://www.pcgameshardware.de)
Reporter | ||
Comment 9•6 years ago
|
||
Indeed a lot better compared to when I reported it. Runs well here on an AMD APU on Linux using the RadeonSI driver, too.
Updated•5 years ago
|
Updated•4 years ago
|
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•