Background not rendering, Blue Background instead

Happens on some system, the system where the picture was taken has an AMD Radeon HD7600M & Intel® HD Graphics 4000.

Some other Graphics Units with the same problem:
Nvidia Geforce 9500 GT, Driver version 342.01
Nvidia Geforce 9800 GT, Driver version Unknown
Nvidia Geforce 545 GT, Driver version: 267.95
Nvidia Quadro FX 3800, Driver version: 342.00
AMD Radeon R9 M200X, second GPU: Intel® HD Graphics 4600
ATI Radeon HD 4650, Driver version: Unknown

[wesselsga]

Are you using the sample distribution of CEF this sample provides or did you build your own? I was wondering if you are able to run the DEBUG version of this app. The D3D11 device is setup with the D3D11_CREATE_DEVICE_DEBUG when running in Debug mode and it should trace out any D3D errors. I can only assume Chromium is unable to create the shared texture on the hardware sets you have listed.

I would also be curious what information is listed in Chrome on any of those machines if you navigate to chrome://gpu in the browser.

I am using the sample distribution of CEF linked in this repo.

How would I go about running the DEBUG version?

[wesselsga]

You would have to build CEF with the pull request which takes quite a bit of time. With D3D11_CREATE_DEVICE_DEBUG the error messages just goto the output of OutputDebugString so you could in theory just comment out the #ifdef on line 765 in d3d11.cpp in this app and simply run the Release build. If you dont have Visual Studio on one of those test machines you can use DebugView to see the trace messages. I'm pretty sure you need the Win10 SDK installed however at a minimum to be able to create a D3D11 device with D3D11_CREATE_DEVICE_DEBUG flag. So it could be a pain if you don't already have VS installed.

I'm trying to dig up an old machine here to see if I can get something reproducible.

I am currently building cef, after I am done and tested again I will get back at you...

Here is the chrome://gpu output btw:

https://pastebin.com/qLhWG8ZM

[winxuser]

if there is anything i can do to help let me know, i also have been having this issue since the 15th march update ot the CEF

[wesselsga]

I reproduced this issue on NVidia GeForce 8400 GS (driver version 342.01). Looks like the code that was added to Chromium setting up the FBO on the D3D11 texture is likely failing. These are the error messages I'm seeing here:

[0414/215616.497:ERROR:gles2_cmd_decoder.cc(4671)] [.DisplayCompositor-0000000009E2EB90]GL ERROR :GL_INVALID_FRAMEBUFFER_OPERATION : glClear: framebuffer incomplete
[0414/215616.498:ERROR:gles2_cmd_decoder.cc(4671)] [.DisplayCompositor-0000000009E2EB90]GL ERROR :GL_INVALID_FRAMEBUFFER_OPERATION : glDrawElements: framebuffer incomplete

I will have to do some more digging to see if this can be resolved.

[winxuser]

that would be great. need anything let me know, ill test new and wonderful things on my old gpu hahah

[wesselsga]

Ok, looks like the issue is setting up the gl pbuffer with the D3D11 texture. The code was using the following for the config attributes on the pbuffer:

EGL_RENDERABLE_TYPE, EGL_OPENGL_ES3_BIT

On older hardware, ES3 isn't available via ANGLE so the call to eglCreatePbufferFromClientBuffer is failing. I updated the sample distribution linked from this project to simply use the EGL_OPENGL_ES2_BIT which hopefully should work. If we can verify this works for your hardware setups listed above - I will integrate this fix into the actual PR for CEF (probably with a fallback mechanism that attempts ES3 first and uses ES2 if that fails)

If you need to build CEF yourself (and don't want to wait for me to update the PR) ... you can make the change in gpu\command_buffer\service\external_texture_manager.cc at line 188.

Thanks!

[blattersturm]

In @Flatracer's chrome://gpu output, I spotted these workarounds existing:

Disable Direct3D11 on systems with AMD switchable graphics: 451420, 755722
Applied Workarounds: disable_d3d11

This might be problematic if Chrome itself wouldn't work without these workarounds at all either - it's likely for the issue with old (feature level 10) GPUs to be distinct from this issue with Intel/AMD or AMD/AMD switchable graphics.

The bugs referred to, for reference, are #451420 and apparently #755722 which shows that Chrome is only meant to apply these workarounds on older drivers.

Driver vendor   Advanced Micro Devices, Inc.
Driver version  15.200.1062.1004
Driver date 8-3-2015

Might it be needed to disable the GPU workaround blacklist using a flag to get this to work on this kind of hardware, and should doing this not be affecting the scenario at all (e.g. if both the mixer as well as Chrome are forced to run on the AMD GPU)?

@wesselsga
Could you send me the new build?
I just have my laptop with me and it would take ages to build it myself.

[blattersturm]

@Flatracer, it seems to be the case the link in the project README to the binary distribution was updated, so only cef-mixer itself would need to be built.

However, if only the above change was made, just dropping in the new Release/ DLLs might work as well.

[winxuser]

What about nvidia gpu's @blattersturm they would give out a different log?

@blattersturm I don't think he updated the repo with the new file, thats the same file I downloaded earlier do build the demo. 🤔

When it is the updated file, it doesn't work, still the same problem.

[wesselsga]

@blattersturm is correct - if disable_d3d11 is being applied by chromium then this definitely will not work.
@Flatracer - the binary distribution was the only thing updated and you should be able to just unzip and drop the new libcef.dll in your bin/ directory.

You could try updating the html_layer.cpp source file in cefmixer and add the --ignore-gpu-blacklist command-line flag in the method OnBeforeCommandLineProcessing.

I'm surprised this wouldn't work on the Nvidia systems you listed? If the last modified date of the libcef.dll is 4/15/2018 6:53 UTC time - you should have the correct latest version.