"WebGL is not supported" with Brave browser

Using Cryosparc 5.0.6 and Brave 1.93.129 (arm64).

I updated CS from 4.7 in June and haven’t used Live until now, so I’m not sure if this error comes with the CS update or a Brave update.

When using Brave, a Chromium browser, in the plot fields in CS Live sessions (e.g. in Overview), I see the error “WebGL is not supported by your browser - visit http://get.webgl.org for more info”.

  1. Following the link, or using other WebGL tests, shows that WebGL is working in other contexts.
  2. I allowed fingerprinting or turned off shields for localhost and did a hard refresh, as suggested by the top google search for this error, to no avail.
  3. In Chrome, I am able to see the plots.
  4. brave://gpu and chrome://gpu both ave the same entry for GL_RENDERER: ANGLE (Apple, ANGLE Metal Renderer: Apple M1, Version 15.7.3 (Build 24G419))
  5. I’m not sure if WebGL is used anywhere else in cryospearc, but I haven’t seen this error outside of a Live session

Any tips to deal with this? Or is it a bug in 5.0.6? I’m happy to run any suggested diagnostics.

Latest Brave build on ARM64 MacOS is 1.93.134, which I’m running right now on an M1 Macbook Pro and don’t see this error with CryoSPARC 5.0.6. Do you get offered an update if you go to Brave → About Brave?

Hi! I have had this issue for a couple of months. That’s why I started using Firefox for the jobs that require WebGL, which until now has only been the Manually Curate Micrographs job. So, once I am done with preprocessing, I switch to Chrome, since cryoSPARC runs smoother there. Not really a fix, but I hope it helps.

Best,

Kristina

Hi @kevinj and @kristinay, this appears to be an issue with older versions of Brave which seems to have been fixed in v1.93.134. Please try upgrading to the latest version and see if that resolves the issue.

If upgrading still does not work, you can disable WebGL in cryoSPARC plots by running localStorage.setItem('cryosparc_enableWebGLAttributePlots', false) in Brave’s console. Be advised that this may lead to performance issues with large quantities of data.

– Ryan

2 Likes