1693205 - Worse results of vsynctester.com on Firefox with Webrender enabled at Linux (Intel HD 5500 GPU)

Status: RESOLVED WORKSFORME

(Core :: Graphics: WebRender, defect, P3)

Description

[Konrad Kołodziejczyk]

Attachment: vsynctest webrender.png

User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.182 Safari/537.36

Steps to reproduce:

I've opened https://vsynctester.com with Webrender enabled and with Basic compositor (Webrender disabled: gfx.webrender.force-disabled option in about:config). I've compared the results.

Actual results:

On Basic compositor I've noticed better result of vsynctester.com. I attach attachments.

Expected results:

I expect the same or better vscyctester.com result on Webrender enabled (GPU acceleration could improve the results). I think this problem is realted to similar problem (low performance with Webrender on Intel HD 5500 at Linux).
https://bugzilla.mozilla.org/show_bug.cgi?id=1634822

Comment 1

[Konrad Kołodziejczyk]

Attachment: vsynctest basic compositor.png

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'Core::Graphics: WebRender' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Comment 3

[Robert Mader [:rmader]]

Note: in basic compositor (on X11) there is no vsync at all. It's just a fixed ~60Hz timer.

Comment 4

[Jeff Muizelaar [:jrmuizel]]

Konrad, can you clarify what you are seeing that is worse?

Comment 5

[Konrad Kołodziejczyk]

(In reply to Jeff Muizelaar [:jrmuizel] from comment #4)

Konrad, can you clarify what you are seeing that is worse?

Lower vsync mark and hills on graph.

Comment 6

[Robert Mader [:rmader]]

Konrad, do you still see a difference in recent versions? I'm asking because WR has improved a lot since the report was opened.

Comment 7

[Konrad Kołodziejczyk]

No, I don't see this problem anymore.

Comment 8

[Robert Mader [:rmader]]

(In reply to Konrad Kołodziejczyk from comment #7)

No, I don't see this problem anymore.

Thanks!