pixbits@ Thanks for the issue.

Unable to reproduce the issue on Mac OS 10.12.6, Windows 7 and Ubuntu 14.04 using the latest Canary 63.0.3230.0 and latest Stable 61.0.3163.100  with the below steps.

1. Launched Chrome and navigated to the above given URL - http://store.steampowered.com/
2. Scrolled the page and could observe that the page is rendering correctly without any squares.

Attached is the screen cast for the same. Please confirm if anything is missed here.

Request you to please retry the issue on a new Chrome profile without any flags/extensions and update the thread if there is any issue.

Thanks...

Deleted: 771006.webm 10.4 MB

	771006.webm 10.4 MB View Download

Hi, it's still me. Thank you for answering.

I just tried with a clean install and all extensions disabled and the issue is showing anyway. But there is a specific thing which could be of help.

I have a two monitor setup, both monitors are calibrated. This issue seems to occur only on the second monitor in the following way: if I open a tab on the second monitor then it has wrong colors and flickering boxes, the afflicted tab keeps being buggy even if I drag Chrome window in the first monitor. If I open a tab on the first monitor then the issue doesn't seem to occur and the tab keep being correct even if I move Chrome window to the second monitor.

I just tested this conditions 30-40 times and every time it just went as I explained above. It's just an empirical deduction but maybe it's related to the problem.

I'm a developer so I'm quite practical with this, if there's anything I can do to help you further understand what could cause the issue just let me know.

Thanks,
Jack 

You can probably bisect the regression (if it's one) yourself:
https://www.chromium.org/developers/bisect-builds-py

I tried to bisect the build and concluded with this:

You are probably looking for a change made after 482902 (known good), but no later than 482905 (first known bad).
CHANGELOG URL:
  https://chromium.googlesource.com/chromium/src/+log/d95e4951a3bab57b4839e3a3d7e64d43c8079d42..19bd384f656790e8e409086b5b97a53b3a6f5921

There is this commit https://chromium.googlesource.com/chromium/src/+/1894d423068be735560e0171922c833c4091b5d1 in that range which enables color correction by default and breaks Chrome for me. Indeed if I disable color correction through chrome://flags then the bugs doesn't manifest.

Now I guess the problem is how color correction is applied/calculated on multiple monitors. I kept experimenting and I still confirm that up to now this happened only on second monitor.

I could try dissecting the build if there's a way to enable color correction through arguments (which doesn't look the case according to https://peter.sh/experiments/chromium-command-line-switches/) for builds before the one which sets it by default on (even because changing it through chrome:://flags while dissecting doesn't work and cause Chromium to crash).

Your bisect info looks plausible so hopefully TE will assign the bug owner accordingly.

>if there's a way to enable color correction through arguments

chrome --enable-features=ColorCorrectRendering

Ok, I did bisection again this time by forcing Color CorrectRendering and I think I found the real cause this time.

You are probably looking for a change made after 482154 (known good), but no later than 482155 (first known bad).
CHANGELOG URL:
  https://chromium.googlesource.com/chromium/src/+log/0182d6f08535bda5f8465ce991f720a8f21b28fc..ab0aab82705d56bc09d6a4fe0a91eb43a610f30e

The commit is the following "color: Replace more instances of ICCProfile with ColorSpace": https://chromium.googlesource.com/chromium/src/+/ab0aab82705d56bc09d6a4fe0a91eb43a610f30e

And it is definitely related to the problem. You can ignore my first bisection since it just helped to understand that the issue was caused by having color correction on. The real problem is here.

Thanks,
Jack

ccameron@, I'm having a hard time tracking the various issues and de-duping. Sorry.

 Issue 771565  has been merged into this issue.

Please attach the ICC profile of the affected monitor. Also please go to about:gpu, print the results to a PDF, and attach that.

Also, could you test with Chrome Canary to see if the bug is fixed there?

ccameron@ Here you are. I tested the issue on Canary channel and it looks like the bug is not present here. I'm still testing. But I'm not even able to find the color correct flag in chrome://flags (which I disabled on my stable to prevent the bug), it looks like it has been replaced by a different color profile override flag, am I wrong?

Deleted: DELL U2413-829D22AC-5A1E-E203-0EFA-0CE0567D1B49.icc 3.2 KB

DELL U2413-829D22AC-5A1E-E203-0EFA-0CE0567D1B49.icc 3.2 KB Download

Deleted: chrome___gpu.pdf 123 KB

chrome___gpu.pdf 123 KB Download

Actually since it states "Disable all known NVidia GPUs other than the Geforce 6xx and 7xx series, which have been tested" and my GPU is a GTX680 shouldn't I have gpu_rasterization enabled?

I think that this was a duplicate of  issue 768724  then. That has been merged to M62 and will roll out soon.