Firefox on Wayland occasionally stops issuing damage calls
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
People
(Reporter: bugzilla, Unassigned)
Details
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0
Steps to reproduce:
This issue is very inconsistent. I used a single firefox window, browsing normally, for about 24 hours while using sway on a hidpi monitor. This has happened both while using WAYLAND_DEBUG and while not using WAYLAND_DEBUG
Actual results:
The window of firefox where this occured (the issue is per-window) would not issue damage calls and thus would not update. The tab bar shows the background color or the tabs that already exist. Clicking between them changes the title and sometimes the page content but would not change the title bar. Hovering also does not work. Sometimes resizing the window or forcing full screen would force a redraw and the new correct tab bar would show up.
Additionally, every frame where the window was visible, WL_DEBUG would output
[1133338,124] wl_display@1.delete_id(852)
[1133338,138] wl_callback@852.done(302398985)
[1133338,146] -> wl_surface@66.frame(new id wl_callback@852)
[1133338,154] -> wl_surface@66.commit()
Expected results:
Tabs should continue to update whenever I mouseover or switch to a different tab. There should only be wayland messages sent when relevant (i.e. an input device has done something or there is a new frame to display). This is how Firefox worked in Firefox 90.
Comment 1•5 years ago
|
||
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•1 year ago
|
||
A lot of fixes have been made to wayland support since and I cannot reproduce those debug messages anymore, please reopen with more details if you still experience this.
Description
•