Gnome Wayland, Debian Testing, Radeon RX480

MOZ_ENABLE_WAYLAND=1 mozregression --good 2020-02-14 --bad 2020-07-14 --pref gfx.webrender.all:true -a https://my.matterport.com/show/?m=xagotPnLxLt

12:31.55 INFO: Last good revision: 92991ac3e69b59cc793e734e98057a52d7a2e823
12:31.55 INFO: First bad revision: ed590162c31911d03a2375ddfd98ba01481e732e
12:31.55 INFO: Pushlog:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=92991ac3e69b59cc793e734e98057a52d7a2e823&tochange=ed590162c31911d03a2375ddfd98ba01481e732e

ed590162c31911d03a2375ddfd98ba01481e732e Martin Stransky — Bug 1646007 [Wayland] Check Wayland dmabuf backend and fallback to a default one, r=jgilbert
da3c1f47c514fc75270fbe81910df3408f528c9c Martin Stransky — Bug 1646007 [Wayland] Check Wayland backend before X11, r=jgilbert

I have two GPUs in my desktop PC, the Intel APU and my dedicated Radeon RX480:
If I explicitly configure the correct GPU (Radeon) via env var, the bug does not occur:
MOZ_WAYLAND_DRM_DEVICE=/dev/dri/renderD129 MOZ_ENABLE_WAYLAND=1 mozregression --launch 2020-07-14 --pref gfx.webrender.all:true -a https://my.matterport.com/show/?m=xagotPnLxLt

Therefore, this bug might be resolved by bug 1588904.
Although DMABUF WebGL has been enabled by default (bug 1646007), the Wayland backend itself isn't yet (bug 1543600).

Also reproducible with Google Maps.

This might be a risk for Fedora, I'm not sure.

Thanks for reporting. That's interesting bug but I have no idea what can cause it if it happens on double GPU system only. Unfortunately I don't have such setup, a typical laptop I have is integrated Intel GPU + dedicated nvidia GPU which is off by default under Wayland. I'll try to get a system with secondary AMD card.

The severity field is not set for this bug.
:jgilbert, could you have a look please?

For more information, please visit auto_nag documentation.

Jan, has this been fixed by bug 1588904 ?

This was most likely fixed by bug 1588904 - please reopen if that's not the case.