High CPU use

[myangelkamikaze]

I don't really know what's going on here, so this is just a description of what I observed. There's a tl;dr at the end.

Recently I upgraded CefSharp from version 92.0.251 to 94.4.50 and a user noticed very high CPU use (changed from 15% to 91%). Version 95.7.141 had the same problem.

After a bit I figured that hardware acceleration isn't enabled, however it was enabled. CPU/GPU

I couldn't reproduce the behavior with hardware acceleration enabled, but I had the same CPU use change with hardware acceleration disabled. After searching for a while, I noticed this comment: #3817 (comment). I noticed that versions 92 and 95 were using different --use-gl parameters, so I tried to change that, but that didn't get applied.

Since I couldn't get a fix with command line arguments, I eventually just deleted the files mentioned in this comment: #3817 (comment). Without those files, the CPU use went back to normal.

My conclusion is that the vulkan implementation will simply kill CPU performance on older hardware, so as a workaround, I'm deleting those files. This workaround doesn't seem ideal, so I'm wondering if there's a way to disable the vulkan software rendering somehow.

Extra: the testing was happening in this twitter thread, I'm linking it in case I forgot anything.
Thread notes:
First tweet is just pointing out the high CPU use.
The image where I'm asking if hardware acceleration is enabled just shows where the option is.
The in game picture is meant to confirm hardware acceleration works, in case it didn't the HP bar would look like this:

tl;dr
The vulkan software rendering can cause very high CPU use on older hardware, is there a way to disable it?

[amaitland]

What did you try exactly? The links I provided in #3817 Have all the information that I'm aware of. I haven't had need to look for additional information.

Chromium decides which rendering implementation to use, you can load chrome://gpu in Chrome or a ChromiumWebBrowser instance to check the GPU status at runtime.

Swiftshader will be removed at some point in the future, so any workaround will only be temporary. I'd suggest attempting to reproduce the issue with chrome and file a bug on the Chromium issue tracker (search for existing first).

[myangelkamikaze]

What exactly, as in command line arguments?

I tried both --use-gl=swiftshader and --use-gl=swiftshader-webgl (and a few others, but reading the links again that was probably pointless). Both of those result in the same behavior:

(should I just copy the whole report from chrome://gpu?)

There are 9 CefSharp.BrowserSubProcess processes. 2 of them have the correct use-gl, 6 don't have the flag and the high CPU use one has this:

So the flag gets set correctly, but one of the processes ignores it?

I'll try to make a minimal reproduction. Does chrome in this case have to be googles release or is any up to date chromium browser, like edge, fine for it?

[amaitland]

It's possible the command line args only worked in a previous version, I've not really done any testing with newer versions.

There are 9 CefSharp.BrowserSubProcess processes. 2 of them have the correct use-gl, 6 don't have the flag and the high CPU use one has this:

If --type=gpu-process has the command line arg set then I would expect that it's passed through correctly.

I'll try to make a minimal reproduction. Does chrome in this case have to be googles release or is any up to date chromium browser, like edge, fine for it?

I don't know for sure, likely Edge Chromium would be fine.