FS#66185 - [firefox] Hardware accelerated WebGL renderer not being used even though it is available
Attached to Project:
Arch Linux
Opened by Mathias Havdal (matte3560) - Thursday, 09 April 2020, 09:54 GMT
Last edited by freswa (frederik) - Sunday, 13 September 2020, 19:24 GMT
Opened by Mathias Havdal (matte3560) - Thursday, 09 April 2020, 09:54 GMT
Last edited by freswa (frederik) - Sunday, 13 September 2020, 19:24 GMT
|
Details
Description:
WebGL appears to be falling back to the mesa llvmpipe renderer, even though a hardware accelerated renderer (mesa radeonsi) is reported in about:support. Additional info: * Appears to be a new issue in Firefox 75.0-1 * Tested with Radeon RX Vega 64 GPU with mesa 20.0.4-1 Steps to reproduce: 1. Check if hardware accelerated renderer is available in about:support 2. Check if hardware accelerated renderer is actually being used (ex. https://webglreport.com/ or alternatively check CPU usage on https://www.shadertoy.com/ ) |
This task depends upon
Closed by freswa (frederik)
Sunday, 13 September 2020, 19:24 GMT
Reason for closing: Fixed
Additional comments about closing: Working as of firefox 80.0.1-1 + mesa 20.1.7-1 with a RX Vega 56.
Sunday, 13 September 2020, 19:24 GMT
Reason for closing: Fixed
Additional comments about closing: Working as of firefox 80.0.1-1 + mesa 20.1.7-1 with a RX Vega 56.
I don't have LD_LIBRARY_PATH set, but the workaround suggested in comment #11 ( https://bugzilla.mozilla.org/show_bug.cgi?id=1455498#c11 ) fixes the issue. Maybe the mesa radeonsi libs are missing from a whitelist of some kind?
I have upgraded intel-media-driver to 20.1.1-1 yesterday before powering down my machine and assume that the problem stems from this upgrade.
libdrm 101 must be using new calls that aren't whitelisted yet.
FS#66351but that was closed as a duplicate.https://gitlab.freedesktop.org/mesa/drm/-/issues/39 looks like the bug report where the root cause of this is investigated.