Rechecked this issue on Ubuntu 14.04 & Ubuntu 17.04 using chrome stable version 61.0.3163.91, unable to reproduce the issue. Screen shot attached. Followed the instruction as provided in the issue. 

Deleted: Background color.png 385 KB

	Background color.png 385 KB View Download

This very much looks like a video card issue, or we would be seeing reports all over.

Could you try something that will help us debug? In DevTools, under the "..." menu, "More Tools", select "Rendering" and then check the "Layer borders" box. I speculate the that color change will occur at tile boundaries. Please include a screen shot if you can.

Indeed, the change in color occurs at the tile boundaries.

Deleted: chrome-rendering.png 54.7 KB

	chrome-rendering.png 54.7 KB View Download

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

That `deeppink` ended up a poor choice of color. I think the difference becomes more apparent in another screenshot using `deepskyblue`.

Deleted: chrome-rend2.png 54.7 KB

	chrome-rend2.png 54.7 KB View Download

Interesting. It's all the empty tiles. I'm guessing we clear the textures with the background color, but maybe it's something else. Anyway, over to the cc compositing folks.

+ccameron: Is this related to https://chromium.googlesource.com/chromium/src/+/1894d423068be735560e0171922c833c4091b5d1

Definitely related to color correct rendering.

It appears that only solid color layers are having issues.
- For solid color layers, we specify the color of the layer in sRGB.
- For non-solid-color layers, we specify pixel colors in the display color space.

These can be ~1/255 or as much as ~2/255 off from each other due to rounding error, but never should they be more than that.

Could you go to about:gpu, print the resulting page as a PDF and attach it here?

I went to `about:gpu` and saved the page as PDF and attached it.

Deleted: chrome___gpu.pdf 83.0 KB

chrome___gpu.pdf 83.0 KB Download

Everything there looks above-board. I'll give it a try on my Linux machine tomorrow.

1. It does not seem to happen with every color. I just tried and went through the CSS color names as suggested by the dev tools, and for many colors I can’t make out a visial difference. This might not be accurate, as there might still be a minor difference that I just can’t perceive.

2. For easier reproducability: http://output.jsbin.com/coyakopivi/

Deleted: Screenshot from 2017-09-22 15-19-46.png 4.7 KB

	Screenshot from 2017-09-22 15-19-46.png 4.7 KB View Download

Still can't reproduce this locally. Can you run:
  xprop -root | grep ICC > icc_profile.txt
and attach the resulting icc_profile.txt?

(btw, in Chrome 61 you can work around this by disabling color correct rendering in about:flags, and in Chrome 62 and beyond, you can work around this by forcing an sRGB color profile in about:flags)

I attached the output as requested.

Disabling color correct rendering resolves the issue as a workaround.

Deleted: icc_profile.txt 6.5 KB

icc_profile.txt 6.5 KB View Download

Re-attaching as a .icc file

Deleted: bug766175.icc 1.8 KB

bug766175.icc 1.8 KB Download

Comment #14 was right disabling "color correct rendering" solved the issue on Ubuntu 16.04 Chrome 61.0.3163.100

Deleted: icc_profile.txt 6.9 KB

icc_profile.txt 6.9 KB View Download

I can no longer reproduce the issue on:

- Ubuntu 17.10
- Chrome 62.0.3202.89

Thanks, I guess this was fixed by 62.