Closed Bug 1786906 Opened 2 years ago Closed 2 years ago

[Wayland] Clicking on extension toolbar icon sometimes triggers graphics errors

Categories

(Core :: Widget: Gtk, defect)

Firefox 105
Unspecified
Linux
defect

Tracking

()

RESOLVED DUPLICATE of bug 1645677
Tracking Status
firefox-esr91 --- unaffected
firefox-esr102 --- unaffected
firefox104 --- unaffected
firefox105 --- wontfix
firefox106 --- disabled
firefox107 --- fixed

People

(Reporter: viktor_jaegerskuepper, Unassigned)

References

(Blocks 1 open bug, Regression)

Details

(Keywords: nightly-community, regression)

Steps to reproduce:

  1. Install the Noscript extension and another extension like uBlock Origin which can show a toolbar popup.
  2. Run Firefox under heavy system load (my system has an old dual core CPU and is very slow because of that) and play a Youtube video (other resource-intensive sites might also work).
  3. Repeatedly click alternately on the Noscript icon and the icon of the other extension (doesn't work immediately), I believe that the Noscript popup is responsible for triggering this bug.
  4. Observe graphics errors like this (in the terminal and in about:support):
[GFX1-]: window is null
[GFX1-]: Failed to create EGLSurface. 5 renderers, 3 active.
[GFX1-]: Handling webrender error 3
[GFX1-]: Fallback WR to SW-WR

These steps might also trigger bug 1743144 (even on Gnome for me), so don't give up too early. :-)

This bug reminded me of bug 1681107 because it is very similar.

I ran mozregression and got:
Last good revision: c7e183234d7d1396b362d90e2e3ae86bec03347b
First bad revision: f2d872dee1e157449c03b60201fc390a75a9968c
Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=c7e183234d7d1396b362d90e2e3ae86bec03347b&tochange=f2d872dee1e157449c03b60201fc390a75a9968c

This points to bug 1784255.

OS: Arch Linux
Observed on Gnome and KDE

Note: I couldn't reproduce this when my system is idle, but playing a Youtube video in the active tab is already enough on my system to "run Firefox under heavy system load", so I guess what that means depends on your system.

:stransky, since you are the author of the regressor, bug 1784255, could you take a look?
For more information, please visit auto_nag documentation.

Flags: needinfo?(stransky)

The bug has a release status flag that shows some version of Firefox is affected, thus it will be considered confirmed.

Status: UNCONFIRMED → NEW
Ever confirmed: true

The number of error messages isn't always the same, only the first three are always there, e.g. I just got:

[GFX1-]: window is null
[GFX1-]: Failed to create EGLSurface. 10 renderers, 8 active.
[GFX1-]: Handling webrender error 3

I verified in about:support that compositing was still "WebRender" and not "WebRender (Software)", so no fallback this time for some reason.

Flags: needinfo?(stransky) → needinfo?(viktor_jaegerskuepper)

Unfortunately my PC is too slow to create a useful screencast. But while I was trying to do that, I accidentally discovered another way to reproduce this bug (no heavy system load required):

  1. Install the "uBlock Origin" extension
  2. Click on its toolbar icon and then click two times on "More" to extend the popup window
  3. Snap the browser window to the left side of the screen (and depending on your screen size shrink it further horizontally so that the uBlock popup opens to the right because of its size)
  4. Click repeatedly on the uBlock toolbar icon (the popup won't close and stays open all the time, but that's another bug I don't care about at the moment) - clicking many times might be necessary
  5. Observe the above mentioned graphics errors

Again, these steps might also trigger bug 1743144. :-)

I ran mozregression again with these STR and got a different result:
Last good revision: 2cbab5d7e2a99011a19f9c9cc3c3724ccd755f5d
First bad revision: e081a91279ccae716d4717ed818fe297a68836aa
Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=2cbab5d7e2a99011a19f9c9cc3c3724ccd755f5d&tochange=e081a91279ccae716d4717ed818fe297a68836aa

This point to bug 1777664, so I assume that bug 1784255 only made the issue additionally occur in the way described at first and I am changing the "Regressed by" field accordingly.

Martin, can you reproduce the issue now?

Flags: needinfo?(viktor_jaegerskuepper) → needinfo?(stransky)
Regressed by: 1777664
No longer regressed by: 1784255

Can you run Firefox (latest nightly) on terminal with MOZ_LOG="Widget:5 WidgetPopup:5" reproduce the issue and attach the log here?
Thanks.

Flags: needinfo?(stransky) → needinfo?(viktor_jaegerskuepper)
Flags: needinfo?(viktor_jaegerskuepper)
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.