1624290 - [Wayland] DMABuf WebGL crash @ gbm_create_device() (AMD Picasso APU)

Status: RESOLVED DUPLICATE of bug 1624743

(Core :: Widget: Gtk, defect, P3)

Description

[GreyXor]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:76.0) Gecko/20100101 Firefox/76.0

Steps to reproduce:

Hello everyone,
i've followed the activation procedure for wayland dmabuf backend for webgl on Martin's blog(https://mastransky.wordpress.com/2020/03/03/webgl-and-fgx-acceleration-on-wayland/)
I set widget.wayland-dmabuf-webgl.enabled
restart firefox
open a webgl demo (https://webglsamples.org/aquarium/aquarium.html for example)

Actual results:

Tab crash and this is my crash report :

https://crash-stats.mozilla.org/report/index/de5fac34-14a7-4ccd-8242-0e68f0200323
https://crash-stats.mozilla.org/report/index/c378c160-f421-48d0-a7d0-4bab30200323

If I reset widget.wayland-dmabuf-webgl.enabled to false. The demo working again.

Expected results:

WebGL demo working

Comment 1

[Martin Stránský [:stransky] (ni? me)]

It crashes here:
https://searchfox.org/mozilla-central/rev/202a285024f174c2d2bf2152d9cba90a03723eab/widget/gtk/nsWaylandDisplay.cpp#371

It crashes at gbm_create_device() call. I wonder what can be wrong here, maybe wrong DRM device or so?

Comment 2

[Martin Stránský [:stransky] (ni? me)]

Can you attach your about:support please?

Comment 3

[GreyXor]

Attachment: Troubleshooting Information

Comment 4

[GreyXor]

(In reply to Martin Stránský [:stransky] from comment #2)

Can you attach your about:support please?
Thanks for the feedback, I've added my about:support just above.

I don't know if that help but :
i'm using Sway and all my about:config is default but
network.security.esni.enabled true
gfx.webrender.all true
widget.wayland-dmabuf-webgl.enabled true

I have AMD Ryzen 3500U (ThinkPad t495s)
Arch Linux (5.6.0-rc7-1-mainline)

Comment 5

[Martin Stránský [:stransky] (ni? me)]

I don't see anything strange here. Can you try to install mesa-dri debug info packages (for the libgallium_dri.so library) and try to get a backtrace by gdb? Some how-to is here:
https://fedoraproject.org/wiki/Debugging_guidelines_for_Mozilla_products#Application_crash
(this one is for Fedora but should apply to other distros too).
Thanks.

Comment 6

[Robert Mader [:rmader]]

Random guess: could have to do with https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/4294

Comment 7

[Darkspirit]

(In reply to GreyXor from comment #0)

https://crash-stats.mozilla.org/report/index/de5fac34-14a7-4ccd-8242-0e68f0200323
https://crash-stats.mozilla.org/report/index/c378c160-f421-48d0-a7d0-4bab30200323

These crashes also have "Crash Address: 0x138".