Thanks, it seems you already pinned down the issue, I'll investigate how to get the newer Mesa in (I think that's provided by a gnome-* snap) and all the following is just for completeness.
> In order to test if the system MESA has the fix while the Chromium snaps does not, I unpacked it and ran the Chromium binary against system libraries.
In general, for testing purposes you can run the unconfined binary directly by calling /snap/chromium/current/usr/lib/chromium-browser/chrome or /snap/firefox/current/usr/lib/firefox/firefox.
You can also verify if an issue is related to hardware acceleration by passing --disable-gpu.
Thanks, it seems you already pinned down the issue, I'll investigate how to get the newer Mesa in (I think that's provided by a gnome-* snap) and all the following is just for completeness.
Can you attach the following information?
--->
snap info chromium firefox
snap connections chromium
snap connections firefox
<---
> In order to test if the system MESA has the fix while the Chromium snaps does not, I unpacked it and ran the Chromium binary against system libraries.
In general, for testing purposes you can run the unconfined binary directly by calling /snap/chromium/ current/ usr/lib/ chromium- browser/ chrome or /snap/firefox/ current/ usr/lib/ firefox/ firefox.
You can also verify if an issue is related to hardware acceleration by passing --disable-gpu.