OffScreen Rendering GPU 2623

[amaitland]

The 2623 branch has been updated to 49.0.2623.110, it will be worth testing again to see if the issue has been resolved in Chromium

[amaitland]

Tested with 3.2623.1396.g0451528 32bit on windows 10, still seeing the same problem.

[nathanm]

We received a similar error. The render process continuously quits and reopens on Windows 10 64-bit.

Code: Select all

[0329/102510:ERROR:gles2_cmd_decoder.cc(12228)] Context lost because SwapBuffers failed.
[0329/102510:ERROR:gles2_cmd_decoder.cc(4471)] Error: 5 for Command kPostSubBufferCHROMIUM
[0329/102510:ERROR:gpu_command_buffer_stub.cc(1224)] Exiting GPU process because some drivers cannot recover from problems.

[zfjon]

This is also happening to me, Windows 7, 32- and 64-bit builds.

Code: Select all

[0331/105521:ERROR:gles2_cmd_decoder.cc(12228)] Context lost because SwapBuffers failed.
[0331/105521:ERROR:gles2_cmd_decoder.cc(4471)] Error: 5 for Command kPostSubBufferCHROMIUM
[0331/105521:ERROR:gpu_command_buffer_stub.cc(1224)] Exiting GPU process because some drivers cannot recover from problems.
[0331/105521:ERROR:gpu_process_transport_factory.cc(652)] Lost UI shared context.
[0331/105522:ERROR:gles2_cmd_decoder.cc(12228)] Context lost because SwapBuffers failed.
[0331/105522:ERROR:gles2_cmd_decoder.cc(4471)] Error: 5 for Command kPostSubBufferCHROMIUM
[0331/105522:ERROR:gpu_command_buffer_stub.cc(1224)] Exiting GPU process because some drivers cannot recover from problems.
[0331/105522:ERROR:gpu_process_transport_factory.cc(652)] Lost UI shared context.
[0331/105523:ERROR:gles2_cmd_decoder.cc(12228)] Context lost because SwapBuffers failed.
[0331/105523:ERROR:gles2_cmd_decoder.cc(4471)] Error: 5 for Command kPostSubBufferCHROMIUM
[0331/105523:ERROR:gpu_command_buffer_stub.cc(1224)] Exiting GPU process because some drivers cannot recover from problems.
[0331/105523:ERROR:gpu_process_transport_factory.cc(652)] Lost UI shared context.

When I hook the gpu process to a debugger I don't get any traps - it just exits and restarts.

[mxz33]

Our project had to revert CEF versions due to this bug, as flickering happened.
Please, it has been dead since 31th March, when will this be looked into?

I suspect that it's a bug with CEF integration of Chromium, since several stable channel releases didn't bring a fix, nor do I think a Chromium bug report was filed.
If there was, can anyone link that?

Also what I noticed that it only occured for select PC's. One could repro, the other didn't have the issue.

[amaitland]

As there are reports that `master` doesn't have the same problem, it's possible this won't be fixed if that's the case. The workaround of disabling the `GPU` is reasonable, there are also other cases where it's required.

[ultimamanu]

Hi guys,

in case this question is still of interest for someone else, I've been running into the same issue (Lost UI shared context and flickering rendering) on win 10 x64 with CEF 3.2623.

So I was ready to downgrade and test version 3.2556, yet in the process, I realized that the version of libEGL.dll and libGLESv2.dll was slightly updated between those two versions of CEF, so I thought I could just give it a try "for the fun", and I simply replaced those 2 dlls in my application folder (replacing the original dlls from CEF 3.2623, with those from CEF 3.2556), while keeping everything else as is.

And guess what ? the error got away and the rendering seems OK now !... Of course, it might be this would have additional bad side effects in some specific conditions, but for me this works fine for now.

And now maybe this could point someone in the proper direction for further investigation: it seems there could be something going wrong in those 2 dlls .

I hope this helps!

[amaitland]

Issue tracking this problem is https://bitbucket.org/chromiumembedded/ ... ng-in-2623

[fokz]

I am having exactly the same issue even with 2704 so I don't think this has been fixed.

The hint about downgrading the libEGL and libGLESv2 to the versions from 2556 actually is kind of 'working'. In my case (Windows 10 x64, Intel HD gpu) it stopped crashing the renderer process but the rendering itself was suspiciously slow and sluggish despite the fact that it was supposed to be gpu accelerated so something is fishy either way.

Any news on this issue? Or best bet for now would be to downgrade to 2556?

[fddima]

Intel HD4600, Windows 10 x64 without any discrete video, integrated only, works fine for me in all cases except for 2623. I'm think it is can be driver dependent or something else.