antaloczi.arnold@ Thanks for the issue.

Unable to reproduce the issue on Mac OS 10.12.6 and Windows 10 using latest Stable 60.0.3112.113 and canary 63.0.3205.0 with the below steps

1. Launched Chrome and can observe that chrome browser is loaded without any issues and no black screen is seen.

Request you please retry the issue on new profile without any flags/extensions and update the thread if the issue still exists.

Thanks..

I disabled all extension, and reset all flags, but no change!

If I disable GPU acceleration, at the time everything works fine.

If I go example: http://naplanya.boon.hu website, minimize the window, and reopen the window, appear the black screen with GPU acceleration.

Hi  antaloczi.arnold@,

Would it be possible to attach the full output of the chrome://gpu page (save as Webpage, Complete). This will help us find a machine to reproduce your issue on. Thanks!

Thank you for providing more feedback. Adding requester "ericrk@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

The most common error seen is:
glSetDrawRectangleCHROMIUM: failed on surface

This seems to be an API which was added as part of the DirectComposition rendering pipeline in Windows. vmiura@, who knows the most about this code at this point?

antaloczi.arnold@, if possible, can you try running chrome with the flag: "--disable-direct-composition" and let us know if this fixes your issue.

To run Chrome with flags on Windows, see instructions here: https://www.chromium.org/developers/how-tos/run-chromium-with-flags

It seems the problem was resolved.

Chrome with --disable-direct-composition flag, is works.

I do not have the error at this time.

Thank you for providing more feedback. Adding requester "ericrk@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

So, a quick solution is to blacklist direct composition on machines with this card. Not sure how much of a perf hit this comes with.

In the long term, we should investigate why direct composition is failing on these machines.

vmiura@, do you have a feel for how bad disabling direct comp is? Is this something we can do until we have a better fix? Or should we bump priority and try to do the right fix more quickly.

ericrk: the impact is small.  Only a limited set of newer laptops will promote to overlays.

Unless we get more of this report, we should try to reproduce the issue first.

Would someone be so kind as to explain what Blink>Compositing could do to help? Just want to be sure we are relevant and that Internals>Compositing was not the intended component (we get a lot of that).

I have the same issue too, my cpu is core m3-7y30, so the gpu is intel hd 615

reproduce steps:
1. open https://www.google.com in Chrome;
2. minimize the chrome window;
3. reopen the chrome window by click the chrome icon in taskbar

then it will show the black screen, but if you move the mouse pointer to the tab bar, it will show the correct content.

Hi all,

We have met the same issue on Chrome (61.0.3163.100) on Intel HD630 with latest released driver 15.46-4771 and here are some findings:
1. We can always reproduce this issue by cleaning all user datas. That is:
   Run chrome as:  chrome.exe --user-data-dir=path/to/an/empty/folder
2. Chrome with --disable-d3d11 doesn't have such issue.

Also we have observed a similar issue about "glSetDrawRectangleCHROMIUM: failed on surface" on latest Chrome Canary on Intel, AMD and Nvidia GPUs：
1. Run Chrome as: chrome.exe --user-data-dir=path/to/an/empty/folder
2. Open Chrome GPU task manager and record the process id of the GPU process
3. Open http://github.com
4. Minimize and reopen the chrome window
You can see the process id of the GPU process has been changed.
5. Open chrome://gpu and pull to the bottom of the page
You can see "glSetDrawRectangleCHROMIUM : failed on surface" and the report on the crash of GPU process "Context lost because SetDrawRectangleCHROMIUM failed".
This issue can be reproduced on:
1. Intel HD630 (22.20.16.4771)
2. NVidia GTX1060 (22.21.13.8494)
3. AMD RX480 (22.19.162.4) 

The fact that the user in #13 can resolve the issue by running with --disable-d3d11 makes me suspect an Angle issue +geofflang and +jmadill.

I have reported the second issue in #13 to  https://crbug.com/773199 .

From the "glSetDrawRectangleCHROMIUM" errors in the log, this is an issue with DirectComposition.  John Bauman used to own this code, I'm not sure who is familiar with it now.

I'm updated to Chrome 62.0.3202.62 (Official) (64 bit), and I'm updated to latest Intel GPU driver x.x.x.4815 (October 10 release), and appear the follow error messages in GPU page:



[2436:6800:1020/151729.338:ERROR:gles2_cmd_decoder.cc(8945)] : [.DisplayCompositor-000001E497395010]GL ERROR :GL_INVALID_OPERATION : glSetDrawRectangleCHROMIUM: failed on surface
[2436:6800:1020/151729.338:ERROR:gles2_cmd_decoder.cc(8946)] : Context lost because SetDrawRectangleCHROMIUM failed.
[2436:6800:1020/151729.338:ERROR:gles2_cmd_decoder.cc(5414)] : Error: 5 for Command kSetDrawRectangleCHROMIUM
[2436:6800:1020/151729.338:ERROR:gpu_channel_manager.cc(197)] : Exiting GPU process because some drivers cannot recover from problems.
GpuProcessHostUIShim: The GPU process exited normally. Everything is okay.
[9104:7012:1020/151730.998:ERROR:gles2_cmd_decoder.cc(8945)] : [.DisplayCompositor-000001E4A3CA68D0]GL ERROR :GL_INVALID_OPERATION : glSetDrawRectangleCHROMIUM: failed on surface
[9104:7012:1020/151730.998:ERROR:gles2_cmd_decoder.cc(8946)] : Context lost because SetDrawRectangleCHROMIUM failed.
[9104:7012:1020/151730.998:ERROR:gles2_cmd_decoder.cc(5414)] : Error: 5 for Command kSetDrawRectangleCHROMIUM
[9104:7012:1020/151730.998:ERROR:gpu_channel_manager.cc(197)] : Exiting GPU process because some drivers cannot recover from problems.
GpuProcessHostUIShim: The GPU process exited normally. Everything is okay.
[5056:3684:1020/151731.807:ERROR:gles2_cmd_decoder.cc(8945)] : [.DisplayCompositor-000001E4A3CA6E20]GL ERROR :GL_INVALID_OPERATION : glSetDrawRectangleCHROMIUM: failed on surface
[5056:3684:1020/151731.807:ERROR:gles2_cmd_decoder.cc(8946)] : Context lost because SetDrawRectangleCHROMIUM failed.
[5056:3684:1020/151731.807:ERROR:gles2_cmd_decoder.cc(5414)] : Error: 5 for Command kSetDrawRectangleCHROMIUM
[5056:3684:1020/151731.807:ERROR:gpu_channel_manager.cc(197)] : Exiting GPU process because some drivers cannot recover from problems.
GpuProcessHostUIShim: The GPU process exited normally. Everything is okay.
[5736:496:1020/151732.901:ERROR:gles2_cmd_decoder.cc(8945)] : [.DisplayCompositor-000001E4A3CA6380]GL ERROR :GL_INVALID_OPERATION : glSetDrawRectangleCHROMIUM: failed on surface
[5736:496:1020/151732.901:ERROR:gles2_cmd_decoder.cc(8946)] : Context lost because SetDrawRectangleCHROMIUM failed.
[5736:496:1020/151732.901:ERROR:gles2_cmd_decoder.cc(5414)] : Error: 5 for Command kSetDrawRectangleCHROMIUM
[5736:496:1020/151732.901:ERROR:gpu_channel_manager.cc(197)] : Exiting GPU process because some drivers cannot recover from problems.
GpuProcessHostUIShim: The GPU process exited normally. Everything is okay.
[7820:6052:1020/151733.752:ERROR:gles2_cmd_decoder.cc(8945)] : [.DisplayCompositor-000001E497395AB0]GL ERROR :GL_INVALID_OPERATION : glSetDrawRectangleCHROMIUM: failed on surface
[7820:6052:1020/151733.752:ERROR:gles2_cmd_decoder.cc(8946)] : Context lost because SetDrawRectangleCHROMIUM failed.
[7820:6052:1020/151733.752:ERROR:gles2_cmd_decoder.cc(5414)] : Error: 5 for Command kSetDrawRectangleCHROMIUM
[7820:6052:1020/151733.752:ERROR:gpu_channel_manager.cc(197)] : Exiting GPU process because some drivers cannot recover from problems.
GpuProcessHostUIShim: The GPU process exited normally. Everything is okay.
[5104:4540:1020/151734.615:ERROR:gles2_cmd_decoder.cc(8945)] : [.DisplayCompositor-000001E497394020]GL ERROR :GL_INVALID_OPERATION : glSetDrawRectangleCHROMIUM: failed on surface
[5104:4540:1020/151734.615:ERROR:gles2_cmd_decoder.cc(8946)] : Context lost because SetDrawRectangleCHROMIUM failed.
[5104:4540:1020/151734.615:ERROR:gles2_cmd_decoder.cc(5414)] : Error: 5 for Command kSetDrawRectangleCHROMIUM
[5104:4540:1020/151734.615:ERROR:gpu_channel_manager.cc(197)] : Exiting GPU process because some drivers cannot recover from problems.
GpuProcessHostUIShim: The GPU process exited normally. Everything is okay.
[4948:8272:1020/151735.387:ERROR:gles2_cmd_decoder.cc(8945)] : [.DisplayCompositor-000001E497395AB0]GL ERROR :GL_INVALID_OPERATION : glSetDrawRectangleCHROMIUM: failed on surface
[4948:8272:1020/151735.387:ERROR:gles2_cmd_decoder.cc(8946)] : Context lost because SetDrawRectangleCHROMIUM failed.
[4948:8272:1020/151735.387:ERROR:gles2_cmd_decoder.cc(5414)] : Error: 5 for Command kSetDrawRectangleCHROMIUM
[4948:8272:1020/151735.387:ERROR:gpu_channel_manager.cc(197)] : Exiting GPU process because some drivers cannot recover from problems.
GpuProcessHostUIShim: The GPU process exited normally. Everything is okay.
[4980:6272:1020/151736.264:ERROR:gles2_cmd_decoder.cc(8945)] : [.DisplayCompositor-000001E497396000]GL ERROR :GL_INVALID_OPERATION : glSetDrawRectangleCHROMIUM: failed on surface
[4980:6272:1020/151736.265:ERROR:gles2_cmd_decoder.cc(8946)] : Context lost because SetDrawRectangleCHROMIUM failed.
[4980:6272:1020/151736.265:ERROR:gles2_cmd_decoder.cc(5414)] : Error: 5 for Command kSetDrawRectangleCHROMIUM
[4980:6272:1020/151736.265:ERROR:gpu_channel_manager.cc(197)] : Exiting GPU process because some drivers cannot recover from problems.
GpuProcessHostUIShim: The GPU process exited normally. Everything is okay.
GpuProcessHostUIShim: The GPU process exited normally. Everything is okay.


I attached the full GPU log.


My GPU: Intel HD 530
My GPU Driver: Intel® Graphics Driver for Windows* 15.47.02.4815.
My OS: Windows 10 Pro x64 1709 latest version
My Browser currently: Google Chrome 62.0.3202.62 (Official release) (64 bit)


Sometimes blinking a black screen.

Deleted: gpu.html 115 KB

gpu.html 115 KB View Download