Firefox WebGL 'NS_ERROR_FAILURE' After Driver Update – Real Fix

You updated your GPU driver and now Firefox throws NS_ERROR_FAILURE on WebGL apps. It's not your web app. It's not Firefox's fault entirely. The new driver changed how it exposes OpenGL, and Firefox's compositor isn't handling it.

The Fix – Three Steps

1. Type about:config in Firefox's address bar. Accept the risk warning.
2. Search for layers.acceleration.disabled. It's almost certainly false by default. Double-click to set it to true.
3. Restart Firefox. Test your WebGL app. It should work now.

If you're still seeing the error after step 3, also search for gfx.webrender.all and set it to false. Then restart again. That's the fallback for newer Firefox versions (89+) that ship with WebRender on by default.

Why This Works

What's actually happening here is a mismatch between the GPU driver's OpenGL implementation and Firefox's accelerated layer manager. The driver update changed how it handles buffer swaps or texture sharing – often seen on Intel UHD Graphics 620, NVIDIA GeForce RTX 30-series, or AMD Radeon RX 6000 cards after a clean driver install.

Setting layers.acceleration.disabled to true tells Firefox to skip GPU compositing for browser layers. It falls back to software rendering for the UI, but WebGL still uses the GPU directly via the <canvas> element. The reason step 3 works is that it removes the conflicting accelerated compositor path, letting WebGL talk to the GPU without the layer manager interfering.

You lose hardware-accelerated page rendering for regular web content (scrolling, animations). In practice, unless you're on a decade-old CPU, you won't notice. WebGL performance remains unchanged because that's a separate code path.

Less Common Variations

AngularJS or React Apps That Freeze, Not Crash

Sometimes the error doesn't show in the console, but the app freezes after a few seconds. Check webgl.out-of-process in about:config. Set it to false. This forces WebGL to run in the main process instead of a sandboxed one, which sidesteps driver threading bugs introduced in newer GPU drivers.

Firefox ESR or Developer Edition

If you're on Firefox ESR (Extended Support Release), you might not have WebRender at all. The fix is the same – layers.acceleration.disabled – but you may also need to set webgl.disable-wgl to true on Windows. This forces Firefox to use ANGLE (DirectX translation layer) instead of raw OpenGL, which older drivers handle more reliably.

Windows Only – DirectX vs OpenGL

On Windows 10 or 11 with certain NVIDIA Studio drivers (522.xx and later), WebGL can fail because Firefox prefers OpenGL over DirectX when both are available. The driver's OpenGL implementation changed shader compilation behavior. Set webgl.prefer-native-gl to false to force ANGLE (DirectX). This is a clean workaround if you need acceleration elsewhere.

Prevention – Lock the Fix So It Doesn't Come Back

Driver updates will re-trigger this if you revert the pref. Here's how to make it stick:

1. In about:config, right-click any of the prefs you changed and select Reset? No – actually leave them. But also create a new boolean pref: security.sandbox.content.shutdown-timeout-sec set to 0. This prevents the sandbox from killing WebGL on slow GPU responses, which some drivers cause after update.
2. Before your next GPU driver update, go to about:config and reset the prefs to false (default). Update the driver. Test. If the error comes back, re-apply the toggles. Firefox won't auto-reset user-set prefs unless you delete the profile.
3. Keep Firefox updated. Mozilla often ships workarounds for specific driver bugs in newer versions. If you're on Firefox 120 or later, check if gfx.webrender.compositor is set to false – that's another safety valve Mozilla added for driver compatibility.

One last thing – don't waste time reinstalling Firefox or rolling back the driver. The toggle above fixes it in 30 seconds. I've seen people spend hours on this. The root cause is the compositor layer, not WebGL itself.