Error creating WebGL context. Three js chrome?

if you have two GPU installed on your system you might want to try to enable Override software rendering list in chrome://flags/

The fix for me was manually enabling WebGL acceleration under Chrome’s feature flags: chrome://flags/

1. Go to your chrome://settings/
2. Click on System, on the left side panel
3. Turn on "Use hardware acceleration when available"
4. Click "Relaunch"

Good luck!

I have encountered this several times with THREE.js. It arises for me once memory resources are shared, abandoned, or overwhelmed, for example:

1. I have a good render loop but then I introduce long tasks.
2. I perform extensive, continuous testing. As I modify live settings in Chrome Inspector, THREE does not reflect all changes without fail. Memory may not be released until I restart.
3. I leave the program running overnight. The next morning the browser is froze, black, OOM...
4. I use multiple instances of a resource, for example Web Audio and Magenta Music. The quality may perceptibly degrade and throw its own errors, but... I will also encounter worse silent errors. For example when I also stream music in another tab, or click audio/video media on Twitter... frozen browser, black screen, WebGL context loss.

I was able to get this working using the following:

Go to chrome://flags/

1. Override Software Rendering List... [X]enabled
2. WebGL Developer Extensions... [X]enabled
3. WebGL Draft Extensions... [X]enabled

Then in settings:

1. Use Graphics Acceleration When Available... [X]enabled

I updated my graphic drivers (NVIDIA) and didn't restart chrome nor the PC, and was having this issue.

I just restarted the PC and now it's fine.

Error creating webGL Context in three.js.min ver 93 I had the same problem with Chrome version 104.5112.102 and managed to fix it by going to Chrome, Settings, and switching off the Use hardware acceleration when available. the graphics card is an old GE Force 8600 card running on Windows 10.

This was resolved for me by simply installing the latest and restarting my browser - thought I'd add it here to hopefully save some future soul from wasting an hour like i did.

For me, I restarted my computer and the error did not appear again. You can try doing this before you do anything more complicated.

For anyone having this problem, it has to do with the Google Chrome browser, what you have to do is click on the three dots on the top right in the browser, and look for settings. There you open the settings and put "Hardware Acceleration" in the search box, activate the switch, and click "Restart".

Remember to ensure that webGL is available before start TresJS:

function isWebGLAvailable() {
  try {
    const canvas = document.createElement('canvas');
    return !!(
      window.WebGLRenderingContext &&
      (canvas.getContext('webgl') || canvas.getContext('experimental-webgl'))
    );
  } catch (e) {
    return false;
  }
}