Try running chrome with the following command line (exit the browser first):
chrome --disable-features=ColorCorrectRendering

If the bug is gone, it's caused by r482904

Yes, issue disappears after running that command.

andylann@ Thanks for the issue.

Unable to reproduce this issue on Windows 7 and Mac OS 10.12.6 using the latest Canary 63.0.3233.0 and Stable 61.0.3163.100 following the below steps.

1. Launched Chrome and navigated to www.google.com page.
2. observed that the Google logo is as expected and no fading is seen.

Note: Launched Chrome normally i.e. not through the command line with disabling any feature as mentioned in comment #1.

Request you to please retry the issue on fresh Chrome profile without any flags/extensions and update the thread if there are any issues.

Thanks..

Issue occurs with a fresh Chrome profile, and also double-checked on 5 different machines (All Windows 10, all using Eizo ColorEdge CG277 monitors). The monitors are set to sRGB with calibrated color profiles.

Thank you for providing more feedback. Adding requester "susanjuniab@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

@ccameron-- Could you please help us in traiging this issue as it has occured due to r482904 as per comment #1 & 2.

Thanks!

Please attach your color profile (the .icc or .icm file).

My prediction is that Chrome is interpreting the color profile correctly. Very few Windows applications actually respect the system color profile -- most of them draw over-saturated content on wide gamut monitors. As a consequence, Chrome is now stuck in the awkward position of having to decide if it should respect the system color profile (which presumably was installed because the user wanted it) or ignoring it (which is what users who didn't intentionally install it usually want).

We have a setting in about:flags to ignore the system color profile. We're considering moving that flag to settings, since many users want it (and about:flags is a sketchy place).

I can also confirm that I am seeing this issue (Chrome 61.0.3163.100 x64, Windows 10). Disabling color correct rendering in chrome://flags does resolve the issue. Attached is my .icm profile.

Deleted: DELL U3011_D65.icm 8.1 KB

DELL U3011_D65.icm 8.1 KB Download

Note: On my iMac, both Safari and latest Chrome (default flags) show colors similar to the Google-logotype at top in my example image. (Not very scientific, I know)

Also note: our Eizo screens at our office is set on sRGB mode. 

Adding my color profile

Deleted: CG277(41214096)_CN_sRGB.icc 3.6 KB

CG277(41214096)_CN_sRGB.icc 3.6 KB Download

Please see instructions in
https://docs.google.com/document/d/1jMokB_OBkZVELu22li8vnHxAUoL1eGnLedP-1Gttv40/edit?usp=sharing

Marking as a duplicate of the WNF  issue 755747 .

WRT the comment:

> I'm using an Eizo monitor with built-in color calibration tools
> that run every night. Those are set up by color management
> professionals.

Most applications (including Edge) do not respect the color profile that is set in Color Management in Windows. Chrome will respect the calibrated color profile. These colors will indeed appear washed out (on a WCG monitor) compared to the over-saturated colors of applications that ignore the color profile.

To see some examples of colors that cannot be rendered without respecting the color calibration, check out
https://webkit.org/blog-files/color-gamut/

I dunno, I'm confused and Windows is broken. Here are some findings with the Chrome Color correct flag set on Enable.

Windows Color Management -> Advanced -> Device Profile: System default (sRGB IEC61966-2.1)
Dell screen Adobe RGB, Dell default color profile, Microsoft Edge: Over-saturated
Dell, Chrome: Over-saturated
Eizo color managed sRGB, Edge: Looks fine
Eizo, Chrome: Looks fine

Test: Windows Color Management -> Advanced -> Device Profile: Wide Gamut RGB
Dell, Edge: Over-saturated
Dell, Chrome: Looks fine
Eizo, Edge: Looks fine
Eizo, Chrome: Washed out

However, I had my Windows on System default before when Chrome looked washed out. Now I cannot seem to get Chrome back to looking washed out with my previous settings.

I'm beginning to think that it was maybe a temp issue that happened during the Chrome update?

Ah, if you have a multi-monitor setup then there may be bugs when moving windows from one monitor to another ( issue 735613 ). These should be fixed in Chrome 62.

Try testing with Chrome Canary -- it should behave correctly.

Of note is that you have to restart Chrome after changing your color profiles to be sure that Chrome picks up the new versions (Windows has no callbacks to tell applications when the profiles change).