OpenGL on MacOS Catalina

[GrzegorzZajac000]

Issue Details

• Electron Version:
  7.0.1
• Operating System:
  macOS Catalina 10.15.1

Expected Behavior

OpenGL is deprecated on macOS Catalina. Can I use Metal API in Electron?

Actual Behavior

I get this error in console:

Unable to create basic Accelerated OpenGL renderer.
Unable to create basic Accelerated OpenGL renderer.
Core Image is now using the software OpenGL renderer. This will be slow.

[MarshallOfSound]

@GrzegorzZajac000 Can you reproduce this error with Chrome?

[GrzegorzZajac000]

This is only thing i can get in about:gpu

Mac Mini 2018 here

[cryptoPickle]

Here is the same issue,

[1] Unable to create basic Accelerated OpenGL renderer.
[1] Unable to create basic Accelerated OpenGL renderer.
[1] Core Image is now using the software OpenGL renderer. This will be slow.

[GrzegorzZajac000]

Any news on this issue?

[nornagon]

Still waiting to hear if this issue is also present in Chrome.

[Ryeonnie]

The same issue too.

Electron version: v7.1.2

[Alecyrus]

https://forums.macrumors.com/threads/core-image-is-now-using-the-software-opengl-renderer-this-will-be-slow.2109425/

[rawbin-]

same in electron 6.x with macOS Catalina 10.15.1

[OVBondHUB]

the same problem macOS Catalina 10.15.1

[nornagon]

More comments reporting the same issue aren't helpful. This is still marked blocked/need-info because we have not yet heard if anyone has tried the same code in Chrome to see if the behavior is the same there. If Chrome behaves fine, but Electron doesn't, then there's maybe something we can do. Otherwise, it's out of our hands.

If you're experiencing this issue, please try to reproduce it in Chrome and let us know how that goes.

[GrzegorzZajac000]

Today I saw new errors, maybe they will be useful for something

[72438:1207/223755.550147:ERROR:gles2_cmd_decoder.cc(18547)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : DoBeginSharedImageAccessCHROMIUM: bound texture is not a shared image
[72438:1207/223755.550161:ERROR:gles2_cmd_decoder.cc(13532)] [.DisplayCompositor]GL ERROR :GL_INVALID_VALUE : glScheduleCALayerCHROMIUM: unsupported texture format
[72438:1207/223755.550308:ERROR:gles2_cmd_decoder.cc(13532)] [.DisplayCompositor]GL ERROR :GL_INVALID_VALUE : glScheduleCALayerCHROMIUM: unsupported texture format
[72438:1207/223755.571869:ERROR:gles2_cmd_decoder.cc(18576)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : DoEndSharedImageAccessCHROMIUM: bound texture is not a shared image```

[niedfelj]

@nornagon I am seeing this on latest Catalina(10.15.2) and latest Chrome (79.0.3945.79 (Versão oficial) 64 bits if I do the following:

Launch Chrome from terminal:

/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome

Go to a site that presumably uses GPU: https://animejs.com

Inspect the site and go into device mode (I'm doing a 4K display mode)

You'll then see at some point (not always right away), this output in the Terminal:

Unable to create basic Accelerated OpenGL renderer.
Unable to create basic Accelerated OpenGL renderer.
Core Image is now using the software OpenGL renderer. This will be slow.

[nornagon]

OK. If this issue is also present in Chrome then unfortunately there's nothing we can do about it. Feel free to file an issue on Chromium's bug tracker: https://crbug.com/new

[pastelsky]

Chrome already has a flag (chrome://flags) that allows you to enable metal rendering. Can the same be done in Electron though @nornagon ?

[nornagon]

You can try enabling the feature for yourself with --enable-features=Metal.

[appleparan]

1. --enable-features=Metal seems doesn't work.
2. Not only Catalina, Mojave also has same problem.
3. Downgrading electron to 6.x doesn't show the error. (Yes, chromium bug, but I don't know how to describe it)

[tboulis]

Any update on this one?

[appleparan]

@tboulis After updating to Electron 8, I'm not getting those messages, even Catalina

[GrzegorzZajac000]

I still have them.
MacOS Catalina 10.15.3
Electron 8

[tboulis]

Me as well @appleparan

[kalbert312]

I'm using Electron 8.0.1 macOS 10.15.3. Still getting them too.

[stevenroussey-privicy]

Chrome 80 itself does use OpenGL on MacOS Catalina.

In Chromium, often things are disabled by default (or enabled!) and the setting is reversed in Chrome. Might this be one of those cases?

On MacOS Catalina, having a backdrop div using blur causes all sorts of white screen / or missing layers for a microsecond, making the screen flash. Nothing is actually running, but the compositor freaks out.

[nathansobo]

I saw the error message a few times in an app I was hacking on last night, but it was unclear what was triggering it. Small sample size so far, but I didn't see any logging after adding the following to the initialization of my app.

import {app} from "electron";
app.commandLine.appendArgument("--enable-features=Metal");

Hopefully I'm not just fooled by randomness here.

–––

Edit: Ugh, just saw the log message again. It didn't work.

[hydrosquall]

Able to reproduce this issue today on a clean install of the electron boilerplate ( https://github.com/sindresorhus/electron-boilerplate ), running Catalina and Electron 7.

[whxleemdddd]

Electron：8.1.1；catalina：10.15.3
Unable to create basic Accelerated OpenGL renderer.
Unable to create basic Accelerated OpenGL renderer.
Core Image is now using the software OpenGL renderer. This will be slow.

[agashish]

Guys, I came with good news and i fix electron app and running locally and .PKg and .DMG all packages are running on @MAC - CATALINA OS.

MY ELECTRON APP IS WORKING SMOOTHLY ON MAC CATALINA EVEN I DO HAVE MAC ON CLOUD. WHICH IS EVEN BETTER TO SERVE THE SOFTWARE.

Thanks Everyone

[athenawisdoms]

Has a solution been found? @agashish @nathansobo

Experiencing the same error sometimes. Running on Catalina 10.15.3 and Electron 8.2.5

[tommoor]

Any chance we could re-open this ticket? It's still an issue in Electron v8, working my way up to testing on v9 – Chrome on left / Electron logs on right. Are we expecting OpenGL to say "Hardware accelerated" in Chrome?

Edit: Seems this only happens when developer tools is open?!

[karimhossenbux]

Yep, it appears to only happen when the devtools is opened.

Found the area where it triggers for me, in the Styles tab:

Video in action: https://imgur.com/a/9wrnv3r