This issue is gone when "Use hardware acceleration when available" option is toggled out. But then I get this issue: https://bugs.chromium.org/p/chromium/issues/detail?id=850636

Sounds similar to bug 893289.
Try running chrome with "--disable-direct-composition" command line.

chrome.exe --user-data-dir=test --disable-direct-composition

The issue remains.

As I can reproduce the issue only in one of two available machines, here is the chrome://gpu/ log in the machine with the issue.

Unable to reproduce the issue on Win-7 and Win-10 using chrome reported version #72.0.3580.0.
Attached a screen cast and gpu_details for reference.

Following are the steps followed to reproduce the issue.
------------
1. Launched chrome using chrome.exe --user-data-dir=test.
2. Did not observe any black rectangles on pages.

vsemozhetbyt@ - Could you please check the issue by creating a new profile without any apps and extensions and please let us know if the issue still persist or not.

Thanks...!!

Deleted: 895142.mp4 1.4 MB

	895142.mp4 1.4 MB View Download

Deleted: win-7_gpu_details.txt 8.8 KB

win-7_gpu_details.txt 8.8 KB View Download

chrome.exe --user-data-dir=test already creates a new fresh profile from scratch without any apps or extensions and with default settings.

Thank you for providing more feedback. Adding the requester to the cc list.

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

Unable to reproduce the issue on another Win-10 machine using chrome reported version #72.0.3580.0. 
It seems the issue is specific to gpu. Hence, forwarding the issue to inhouse team for further triaging of the issue on any win-7 machine.

Thanks...!!

Unable to reproduce this issue on Win 7 with chrome Canary #72.0.3582.0, didn't observe any black rectangle boxes.

Since TE doesn't able to reproduce the issue, adding TE-NeedsTriageHelp label for further triage from dev team.

After I'd launched the Canary with --reset-variation-state flag and then restarted several times with this flag, the issue has disappeared. So the cause may be in some field trials.

It is field trials I just opened another issue because certain recent "flavors" of Chrome DEV now have EVERY DROPDOWN THE SAME BLACK unreadable unless you disable all gpu acceleration at which time they become readable.  Perform a reset of variation and app state is light a friggin light-switch I can reproduce 100% of the time that it's almost every other reset and if you read my issue you will see in my testing I have found (at least currently) a single tell-tale visual indicator of whether you have the "broken" variation flavor or not:

https://bugs.chromium.org/p/chromium/issues/detail?id=898689

report: can you enable hardware acceleration and then re-record the about:gpu page? The current one is running through SwiftShader, so some info are lost?

and about:version with and without the --reset-variation-state

Hardware acceleration was enabled. The issue is currently gone as it seems I've reset the culprit variation. If I manage to get the issue back with a fresh profile, I will try to post about:gpu and two about:version.

It's still worth providing the new about:version to us. So we know which ones do NOT cause the issue.

Can reproduce with these steps:

1. Fresh start with a new profile creation:

chrome.exe --user-data-dir=test

The issue is present (black rectangles in about:welcome content and browser omnibox). See first-start.with-issue.gpu.txt and first-start.with-issue.version.txt

2. Second launch with the created profile:

chrome.exe --user-data-dir=test

The issue is present (the same). See second-start.with-issue.gpu.txt and second-start.with-issue.version.txt

3. Several launches with reset:

chrome.exe" --user-data-dir=test --reset-variation-state

till the issue is gone. See after-some-reset-variation-state.without-issue.gpu.txt and after-some-reset-variation-state.without-issue.version.txt

Deleted: first-start.with-issue.gpu.txt 53.9 KB

first-start.with-issue.gpu.txt 53.9 KB View Download

Deleted: first-start.with-issue.version.txt 758 bytes

first-start.with-issue.version.txt 758 bytes View Download

Deleted: second-start.with-issue.gpu.txt 52.3 KB

second-start.with-issue.gpu.txt 52.3 KB View Download

Deleted: second-start.with-issue.version.txt 2.2 KB

second-start.with-issue.version.txt 2.2 KB View Download

Deleted: after-some-reset-variation-state.without-issue.gpu.txt 11.0 KB

after-some-reset-variation-state.without-issue.gpu.txt 11.0 KB View Download

Deleted: after-some-reset-variation-state.without-issue.version.txt 2.1 KB

after-some-reset-variation-state.without-issue.version.txt 2.1 KB View Download

Thanks. I just learned this afternoon that we could get the variations command by going to chrome://version/?show-variations-cmd

Can you generate the three version texts one more time? That would save significant amount of time on my side.

With ?show-variations-cmd:

Deleted: first-start.with-issue.version.show-variations-cmd.txt 1.2 KB

first-start.with-issue.version.show-variations-cmd.txt 1.2 KB View Download

Deleted: second-start.with-issue.version.show-variations-cmd.txt 23.9 KB

second-start.with-issue.version.show-variations-cmd.txt 23.9 KB View Download

Deleted: after-one-reset-variation-state.without-issue.version.show-variations-cmd.txt 24.2 KB

after-one-reset-variation-state.without-issue.version.show-variations-cmd.txt 24.2 KB View Download

vsemozhetbyt@gmail.com: can you try a few extra things?

1) run with --disable-direct-composition-layers and see if it makes a difference (originally you tried --disable-direct-composition, which no longer exists in Chrome Canary)

2) when you get Chrome to run OK through --reset-variation-state, can you run Chrome again with the last line command line switches from second-start.with-issue.version.show-variations-cmd.txt and see if the bug shows? The command line switches are long, and copy and paste to a terminal may get it cut short, so it's better to create a .bat file and run Chrome through that.

Thanks for your help.

zmo@chromium.org Unfortunately, I cannot anymore reproduce the issue with a new profile. And when I try to force it with a mentioned bat file (attached), I get the error in the console: The system cannot find the file specified. I suspect some chars should be escaped in this bat file, But I am not sure what chars and in what way.

Deleted: c.bat 21.8 KB

c.bat 21.8 KB View Download

Thanks for trying. Let me analyze the data you provided and see if they can shed some lights.

One more thing to try: in  crbug.com/898689 , the reporter figured out the blackness is caused by --enable-zero-copy. Can you try this switch and see if this did cause the issue you were facing before?

By the way, I figured out why the .bat failed to launch Chrome.

--force-fieldtrials="aaa", you need to get rid of "". if it's --force-fieldtrials=AAA, then Chrome launches fine. I don't know why this commandline switch has this special treatment though.

This issue has an owner, a component and a priority, but is still listed as untriaged or unconfirmed. By definition, this bug is triaged. Changing status to "assigned". Please reach out to me if you disagree with how I've done this.