1695918 - [wayland] Flickering and visual update failures on some menus

Status: RESOLVED DUPLICATE of bug 1694967

(Core :: Widget: Gtk, defect, P3)

Description

[luis.pabon]

Attachment: recording.mp4

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

Steps to reproduce:

• Install firefox-nightly (88.0a1hg20210302r569124-0ubuntu0.21.04.1~umd1)
• Create new firefox profile
• Install some add-ons (ublock origin & bitwarden)

Ubutu 21.04 hirsute
Sway 1.5

Actual results:

Opening the add-on dialogs on the top bar malfunctions. Particularly, it draws the first frame and then it stops, only refreshing when hovering with the mouse pointer. Or it flickers. Or it does not draw at all (although the dialog is actually there).

This happens with or without activating webrender.

It not only happens on add-ons, but it is more easily and consistently reproducible on it. Other places that display sporadic but similar weirdness:

• On pages, select drop downs
• On firefox, on the hamburger menu

See attached screen recording of the issue on latest firefox nightly on a new profile.

Expected results:

It works normally.

Comment 1

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

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

Comment 2

[Martin Stránský [:stransky] (ni? me)]

Please test latest nighly (88) under Wayland.
Thanks.

Comment 3

[Martin Stránský [:stransky] (ni? me)]

Also please attach content of your about:support page.

Comment 4

[luis.pabon]

Hi Martin. The test above was already with FF nightly (88.0a1hg20210302r569124-0ubuntu0.21.04.1~umd1) and on an empty profile.

Attaching about:support.

Comment 5

[luis.pabon]

Attachment: support.txt

Comment 6

[Martin Stránský [:stransky] (ni? me)]

I expect disabled WebRender [1] will fix that, correct?
[1] https://fedoraproject.org/wiki/How_to_debug_Firefox_problems?rd=Bug_info_Firefox#Check_WebRender

Comment 7

[luis.pabon]

I have just now force-disabled webrender to test that too (looks like my laptop config qualifies for webrender autoenable) but the issue persists.

Comment 8

[luis.pabon]

Attachment: recording-no-webrender.mp4

Comment 9

[Martin Stránský [:stransky] (ni? me)]

If you see that with both WebRender and Basic backends it looks like wayland compositor bug / gfx driver bug then.

Comment 10

[luis.pabon]

I would say it's unlikely to be sway as Firefox has been working fine with it for some time. Perhaps a gfx bug? Is there any way to get meaningful logs that could say one way or another?

On the other hand, if it were a driver bug, would it not also happen when running under Xwayland (it does not)?

Comment 11

[Martin Stránský [:stransky] (ni? me)]

When mouse cursor melts with window content it's usually HW/driver/compositor specific as the cursor is handled on lower level and it's not painted by application itself.

Comment 12

[luis.pabon]

Thank you and copy that, I'll report to the compositor see if I can get to the bottom of this. I haven't seen any other apps exhibiting this behaviour though, is there anything special about the way these menus are rendered?

Comment 13

[Martin Stránský [:stransky] (ni? me)]

(In reply to luis.pabon from comment #12)

Thank you and copy that, I'll report to the compositor see if I can get to the bottom of this. I haven't seen any other apps exhibiting this behaviour though, is there anything special about the way these menus are rendered?

Yes, we use many hack to render wayland popups.

Comment 14

[luis.pabon]

Attachment: recording-no-webrender.mp4

@Martin, I've actually managed to ascertain this is a regression of some kind between firefox 86 and firefox 87. I've downloaded & tested from https://ftp.mozilla.org/pub/firefox/releases/ to discard any weirdness that could come from Ubuntu's packaging.

See screen recording.

Comment 15

[luis.pabon]

Attachment: recording-bisect.mp4

Apologies, I uploaded the wrong screengrab on my earlier comment. This is the correct one showing FF 86 working correctly and 87b1 having the problem.