I visited the same page recently in Windows 10 x86_64 and did not see this problem.

jrw@ Thanks for the issue.

Able to reproduce the issue on Windows 7 and Ubuntu 14.04 using the latest Stable 62.0.3202.62 and Canary 64.0.3248.0.
Issue is not observed on Mac OS 10.12.6.
This is a Non-Regression issue as this issue is observed from M50 chrome builds.Attached is the screen shot for reference.

Marking this as 'Untriaged' for further updates from Dev.

Thanks.

Deleted: 777505.png 385 KB

	777505.png 385 KB View Download

I can't reproduce on linux M62 or tip of trunk, nor on Windows M62.

Could those who can reproduce please paste the contents of chrome://gpu into this bug report.

I've attached the content of chrome://gpu, but I don't think it's going to do much good, because I have another Chrome profile running where the bug doesn't show up, and the contents of chrome://gpu for both profiles are identical except for the timestamp.

Deleted: gpu_bad.txt 34.3 KB

gpu_bad.txt 34.3 KB View Download

If the behavior differs between profiles then what happens when you disable all extensions, or at least as many as you can?

Also, do the settings in chrome://flags differ between profiles? I know that's annoying to compare, but it would be extremely informative.

At least for me, those "PNGs" are actually WebPs. The artifacts looks somewhat similar to what a WebP image with alpha looks like when you lose/drop the alpha channel. Could this be the bug where a caching proxy reencodes the image as WebP? (I'll see if I can find the bug I'm thinking about...)

 Issue 747640  was the one I was thinking about (and I just checked, and the images here appear to have been subject to Cloudflare massage.)

I can see the problem in incognito mode regardless of which profile I spawn the window from.  I checked the flags, and both profiles have the same settings.  I'm pretty sure they're all the default settings; I reset the flags and restarted Chrome just to be sure, and I'm still seeing the same results as before.

The NextAction date has arrived: 2017-11-06

I'm passing this over to the teams dealing with image formats and decoding, as that seems the likely problem (unless it's loading gone bad).

It would still be really good to figure out what causes the different behavior with different users. Might be Win7 but not Win10, and/or only some linux machines. Is that a GPU vs. CPU decoding issue maybe?