ThreeJS on Firefox stopped working today

Questions
,
1

Today ThreeJS stopped working in Firefox. It works in the other browsers.

When I open the Teapot example from the Threejs website, I get this output in the console:

THREE.WebGLRenderer 102 [three.js:22442:3](https://threejs.org/build/three.js)
THREE.WebGLRenderer: Error creating WebGL context. [three.js:22619:4](https://threejs.org/build/three.js)
Error: WebGL warning: getContext: Disallowing antialiased backbuffers due to blacklisting. [WebGL.js:13:50](https://threejs.org/examples/js/WebGL.js)
Error: WebGL warning: <SetDimensions>: Refused to create native OpenGL context because of blacklist entry: [WebGL.js:13:50](https://threejs.org/examples/js/WebGL.js)
Error: WebGL warning: <SetDimensions>: Failed to create WebGL context: WebGL creation failed: * Refused to create native OpenGL context because of blacklist entry: * Exhausted GL driver options. [WebGL.js:13:50](https://threejs.org/examples/js/WebGL.js)
Error: WebGL warning: getContext: Disallowing antialiased backbuffers due to blacklisting. [WebGL.js:13:82](https://threejs.org/examples/js/WebGL.js)
Error: WebGL warning: <SetDimensions>: Refused to create native OpenGL context because of blacklist entry: [WebGL.js:13:82](https://threejs.org/examples/js/WebGL.js)
Error: WebGL warning: <SetDimensions>: Failed to create WebGL context: WebGL creation failed: * Refused to create native OpenGL context because of blacklist entry: * Exhausted GL driver options. [WebGL.js:13:82](https://threejs.org/examples/js/WebGL.js)
Error: WebGL warning: getContext: Disallowing antialiased backbuffers due to blacklisting. [three.js:22589:22](https://threejs.org/build/three.js)
Error: WebGL warning: <SetDimensions>: Refused to create native OpenGL context because of blacklist entry: [three.js:22589:22](https://threejs.org/build/three.js)
Error: WebGL warning: <SetDimensions>: Failed to create WebGL context: WebGL creation failed: * Refused to create native OpenGL context because of blacklist entry: * Exhausted GL driver options. [three.js:22589:22](https://threejs.org/build/three.js)
Error: WebGL warning: getContext: Disallowing antialiased backbuffers due to blacklisting. [three.js:22589:74](https://threejs.org/build/three.js)
Error: WebGL warning: <SetDimensions>: Refused to create native OpenGL context because of blacklist entry: [three.js:22589:74](https://threejs.org/build/three.js)
Error: WebGL warning: <SetDimensions>: Failed to create WebGL context: WebGL creation failed: * Refused to create native OpenGL context because of blacklist entry: * Exhausted GL driver options. [three.js:22589:74](https://threejs.org/build/three.js)
Error: WebGL warning: getContext: Disallowing antialiased backbuffers due to blacklisting. [three.js:22593:10](https://threejs.org/build/three.js)
Error: WebGL warning: <SetDimensions>: Refused to create native OpenGL context because of blacklist entry: [three.js:22593:10](https://threejs.org/build/three.js)
Error: WebGL warning: <SetDimensions>: Failed to create WebGL context: WebGL creation failed: * Refused to create native OpenGL context because of blacklist entry: * Exhausted GL driver options. [three.js:22593:10](https://threejs.org/build/three.js)
Error: Error creating WebGL context.

I am using Firefox 65.0.1, on Ubuntu 18.10

2

It’s working fine for me. Same version of FF on windows.

3

It might by a Linux or Ubuntu thing, or just my computer. It most definitely does not go away when I set this:

layers.acceleration.force-enabled=true in about:config

Which is the only suggestion I could find with Google. There I found that there are different GPU blacklists for different operating systems.

4

It could be that your GPU/driver is on the blocklist:

https://wiki.mozilla.org/Blocklisting/Blocked_Graphics_Drivers

2 Likes
5

That is exactly what the setting above is supposed to overrule. But I will dive into that a bit deeper.

6

The wiki page cited suggests the setting you need is
webgl.force-enabled=true . not “layers.acceleration” which is for compositing of the components of standard HTML elements.

1 Like
7

Thanks, the other setting was from another site. But this setting has no result in my case either… I also tried webgl.msaa-force…

8

I wonder if it has anything to do with Ubuntu switching to Wayland and not presenting the X11 environment FF is expecting, not something I’ve played with.

9

Ubuntu 18.10 uses X11 by default, and I checked to see if mine does too – it does.

Today the problem is gone.

1 Like