Closed Bug 1731251 Opened 3 years ago Closed 3 years ago

Extension pop-up windows have a black border, no transparency

Categories

(Core :: Graphics, defect)

x86_64
Linux
defect

Tracking

()

RESOLVED DUPLICATE of bug 1731125

People

(Reporter: gcp, Unassigned)

References

(Regression)

Details

(Keywords: regression)

Attachments

(1 file)

Every extension with a pop-up window in the address bar (e.g. uBlock Origin, MyQOnly, 1Password) now has a black background where it should be transparent.

Ubuntu 20.04, NVIDIA GTX 1060, NVIDIA proprietary drivers 470.57.02

Bisecting yields a range including bug 1670545 and bug 1695933. Likely, bug 1695933 is the cause and bug 1670545 is a startup crash that breaks the bisection.

Keywords: regression
Regressed by: 1695933
Has Regression Range: --- → yes
Version: unspecified → Trunk
Attached file about:support
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → DUPLICATE

(In reply to Gian-Carlo Pascutto [:gcp] from comment #0)

bug 1670545 is a startup crash that breaks the bisection.

It should have no effect on proprietary Nvidia.
A startup crash could occur before bug 1670545 if one was using Mesa and had manually set the mesa_glthread=true environment variable.
Some users might have manually added it to ~/.profile to speed up some GLX games.
To prevent them from suddenly running into the crash, Firefox enforces mesa_glthread=false for itself.

Regarding thread safety I also remember bug 1699433.

Btw, the Linux CI image is too old to test newer features that are already shipped downstream: bug 1725245
(It would be great if you could influence prioritization.)

I don't have that env var, and the bisection ends up on this range: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=7c989d792b2d8d38f7c6138bf39918aa79046750&tochange=b50ef8e31c4c2dd8993366c68c2f6f87e5a4f68a

Which only has those 2 bugs in it. It's hard to continue bisecting here because most of the builds crash on startup. Hence my suspicion about the relevant bugs.

Btw, the Linux CI image is too old to test newer features that are already shipped downstream: bug 1725245
(It would be great if you could influence prioritization.)

I'll explain the risk from not having testing coverage, but it does look like some of the right people are already in that bug.

(In reply to Gian-Carlo Pascutto [:gcp] from comment #4)

I don't have that env var, and the bisection ends up on this range

Yes, bug 1695933 caused (enabled) this black border bug.

because most of the builds crash on startup.

It would be good to know that those are not caused by bug 1695933:
Do such crashes still occur with recent autoland builds or even with regular Nightly?
Do you use Gnome X11 (=compositing enabled) or something else with disabled compositor?

(For example, bug 1730991 can occur with GLX and manually enabled GPU process, but bug 1716114 occured even with Intel and without GPU process.)

Do such crashes still occur with recent autoland builds or even with regular Nightly?

I'm using Nightly and it's not crashing on startup.

Do you use Gnome X11 (=compositing enabled) or something else with disabled compositor?

Kubuntu 21.04 so KDE. Settings seems to suggest a Compositor with an OpenGL 3.1 backend. (about:support is attached)

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: