When running firefox-wayland (1) sometimes (2) new tabs stop rendering, they are clearly loading (spinner is shown on the tab) and I do believe they do actually render, but the final blit of the rendered result to the tab does not happen.
When I tear the tab away from the firefox-window, so that it becomes a new-window then it does instantly show, showing that it has fully loaded (and rendered) but just is not shown.
When this happens the minimize, maximize and close buttons on the affected firefox window also stop working (I'm using CSD). This is a per window thing, new tabs in other firefox windows work fine, the min/max/close buttons on other windows also work fine.
When this happens I'm seeing various messages about IPC problems in my journal,
as such I think this may be related to bug 1585332, note firefox does not crash for me.
1) I think this is firefox-wayland only
2) Seems to happen mostly when having one or more tabs with youtube open
(In reply to Hans de Goede from comment #0)
> When running firefox-wayland (1) sometimes (2) new tabs stop rendering, they
> are clearly loading (spinner is shown on the tab) and I do believe they do
> actually render, but the final blit of the rendered result to the tab does
> not happen.
I'm seeing this too. Note that once the first new tab has stopped rendering, no new tab in old windows can render any more. This issue has been present for a while (at least before 66.0.2), but I don't know how old it really is.
This seems to no longer be happening with the 67.0 release, closing.
(In reply to Hans de Goede from comment #2)
> This seems to no longer be happening with the 67.0 release, closing.
I celebrated too soon, I did not see this for about a week, but it just happened again, re-opening.
One new thing which I did learn is that I can still click on elements of the non visible page and then I get taken to other parts of the site. So everything seems to be working fine, except that the contents is not visible.
I've not seen this since that 1 time this triggered again on 6-6, so lets close this again.
Not fixed... I'm still experiencing this bug on Fedora 30 (Workstation Edition) with Firefox on Wayland 68.0.2
Firefox on Wayland works for a while, then suddenly new tabs are rendered blank (just a solid sheet of white). Also, when the blank tabs appear and all rendering in other tabs stop. Clicking on the "hamburger menu" in the upper right results in nothing appearing.
Restarting Firefox on Wayland fixes the issue temporarily, all tabs render again, the hamburger menu works, until an indeterminate amount of time passes, then the blank window rendering bug appears again.
Hardware: Lenovo ThinkPad T560, Intel GPU, 3K screen scaled at 2x. Running default GNOME session on Wayland.
Can you please try latest mozilla nightly? how-to is here:
Also disable webrender at nightly (at about:config) as it's default for nightly now.
Firefox on Wayland has improved since my last post in August. I am currently on Firefox 69.0.3 on Fedora 30.
The only remaining regression relative to Firefox on Xwayland is the toolbar dropdown menus (such as Bookmarks) fail to appear after clicking, but eventually do appear once the cursor is moved off the toolbar into the browser content window.
I have a second Fedora 30 system (Intel NUC) that I will test and post what I find here.
I downloaded the FF 71 nightly and ran it on my ThinkPad, via the terminal command:
MOZ_ENABLE_WAYLAND=1 ./firefox -ProfileManager -no-remote'
I did not notice the issues with the drop down toolbar menus described in Comment 7. Everything worked as it should.
Can you please also try Firefox 70 from koji? - https://koji.fedoraproject.org/koji/packageinfo?packageID=37
I just installed the Firefox 70.0-1 & Firefox Wayland 70-0.1 RPMs from Koji and it works perfectly. Dropdown menus appear immediately upon clicking toolbar bookmarks and hamburger icons. Thumbs up here.