1824579 - SW WR: Edge glitch Problem with buttons, div and etc.

Status: RESOLVED INVALID

(Core :: Graphics: WebRender, defect)

Description

[lucifer25x]

Attachment: Screenshot from ecosia.

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/111.0

Steps to reproduce:

I opened ecosia.org and web.telegram.org/k/ in Firefox.

Actual results:

Some elements (buttons, and messages in telegram) seem to have problematic edges and glitch changes when I hover over these elements. I don't know if it's related to SVG.

Expected results:

Everything should work without problem and edges should look normal, without any glitch.

Comment 1

[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 correct in case you think the bot is wrong.

Comment 2

[Sotaro Ikeda [:sotaro]]

Hi lucifer25x, can you attach about:support to this bug?

Comment 3

[Sotaro Ikeda [:sotaro]]

:gw, can you comment to the bug?

Comment 4

[Darkspirit]

(In reply to lucifer25x from comment #0)
Please open about:support in your address bar, click on "Copy text to clipboard" and paste it here. Thanks!

Comment 5

[lucifer25x]

Attachment: about:support

(In reply to Sotaro Ikeda [:sotaro] from comment #2)
> Hi lucifer25x, can you attach about:support to this bug?

Comment 6

[lucifer25x]

Attachment: about:support

(In reply to Sotaro Ikeda [:sotaro] from comment #3)
> :gw, can you comment to the bug?

Comment 7

[lucifer25x]

Attachment: Application Basics.txt

Comment 8

[lucifer25x]

(In reply to Sotaro Ikeda [:sotaro] from comment #3)

:gw, can you comment to the bug?

Sorry for late reply

Comment 9

[Glenn Watson [:gw] | PTO until 29th April]

Interestingly this is occurring with sw-wr, as Firefox fails to detect any GPUs in glxtest. It looks like the graphics hardware in general is broken, so you'll likely be getting quite slow rendering performance as the GPU isn't being used.

Do you know what kind of GPU is in this machine? Could you also post the output of running glxinfo in a terminal here?

The edge glitch issue is probably something separate but it might be useful to see if it occurs in hardware mode as well on your machine.

Comment 10

[lucifer25x]

Attachment: glxinfo.txt

Comment 11

[lucifer25x]

(In reply to Glenn Watson [:gw] from comment #9)

Interestingly this is occurring with sw-wr, as Firefox fails to detect any GPUs in glxtest. It looks like the graphics hardware in general is broken, so you'll likely be getting quite slow rendering performance as the GPU isn't being used.

Do you know what kind of GPU is in this machine? Could you also post the output of running glxinfo in a terminal here?

The edge glitch issue is probably something separate but it might be useful to see if it occurs in hardware mode as well on your machine.

Hi, I added output of the command as an attachment. Thanks.

Comment 12

[lucifer25x]

(In reply to Glenn Watson [:gw] from comment #9)

Interestingly this is occurring with sw-wr, as Firefox fails to detect any GPUs in glxtest. It looks like the graphics hardware in general is broken, so you'll likely be getting quite slow rendering performance as the GPU isn't being used.

Do you know what kind of GPU is in this machine? Could you also post the output of running glxinfo in a terminal here?

The edge glitch issue is probably something separate but it might be useful to see if it occurs in hardware mode as well on your machine.

GPU: AMD ATI Radeon HD 6610M/7610M
GPU: AMD ATI Radeon HD 7660G

Comment 13

[Glenn Watson [:gw] | PTO until 29th April]

Andrew, any ideas why glxtest seems to fail on this machine?

Comment 14

[Darkspirit]

comment 10 = AMD.
SW WR seems to be used due to bug 1787182.

Comment 15

[lucifer25x]

(In reply to Glenn Watson [:gw] from comment #13)

Andrew, any ideas why glxtest seems to fail on this machine?

Hey, still has no idea what's the problem? Pages aren't loading so slow, a while ago WebGL wasn't working sometimes, but now it's working as well. The only problem is the glitch problem for now.

Comment 16

[Darkspirit]

Does the glitch also occur with latest Nightly?
$ pip3 install mozregression
Software rendering:
$ ~/.local/bin/mozregression --launch 2023-05-03 --pref gfx.webrender.software:true -a https://www.ecosia.org/ -a https://web.telegram.org/k/
Hardware rendering:
$ ~/.local/bin/mozregression --launch 2023-05-03 --pref gfx.webrender.all:true -a https://www.ecosia.org/ -a https://web.telegram.org/k/

Comment 17

[lucifer25x]

(In reply to Darkspirit from comment #16)

Does the glitch also occur with latest Nightly?
$ pip3 install mozregression
Software rendering:
$ ~/.local/bin/mozregression --launch 2023-05-03 --pref gfx.webrender.software:true -a https://www.ecosia.org/ -a https://web.telegram.org/k/
Hardware rendering:
$ ~/.local/bin/mozregression --launch 2023-05-03 --pref gfx.webrender.all:true -a https://www.ecosia.org/ -a https://web.telegram.org/k/

I didn't try firefox-nightly but tried the flatpak version. Flatpak version does not have the same problem. I'll try the Nightly version soon.

Comment 18

[lucifer25x]

(In reply to Darkspirit from comment #16)

Does the glitch also occur with latest Nightly?
$ pip3 install mozregression
Software rendering:
$ ~/.local/bin/mozregression --launch 2023-05-03 --pref gfx.webrender.software:true -a https://www.ecosia.org/ -a https://web.telegram.org/k/
Hardware rendering:
$ ~/.local/bin/mozregression --launch 2023-05-03 --pref gfx.webrender.all:true -a https://www.ecosia.org/ -a https://web.telegram.org/k/

I think the errors are related to proprietary AMD drivers. I faced the same issue after installing proprietary AMD drivers on a different system (fedora).

Comment 19

[lucifer25x]

The issue was resolved after the latest mesa drivers update in Fedora 38.

Comment 20

[Darkspirit]

(In reply to lucifer25x from comment #19)
Does the problem still occur after setting gfx.webrender.software to true on about:config and restarting Firefox?
(Please don't forget to set it back to false after this test.)

Comment 21

[lucifer25x]

(In reply to Darkspirit from comment #20)

(In reply to lucifer25x from comment #19)
Does the problem still occur after setting gfx.webrender.software to true on about:config and restarting Firefox?
(Please don't forget to set it back to false after this test.)

After the latest mesa drivers update the problem no longer occurs, everything (including web rendering) works fine.