Assigning to geofflang@ to take a look due to being owner of the related  issue #691262 .

Unable to reproduce the issue on reported chrome version 64.0.3282.140 and on the latest canary 66.0.3341.0 using Windows 10 with the below mentioned steps.
1. Launched Chrome
2. Navigated to https://cointrackr.com/
We didn't observe any trails while loading. Attaching the screen cast for reference.

@geofflang: Could you please help in triaging the issue further.

Thanks!

Deleted: 809087.mp4 2.5 MB

	809087.mp4 2.5 MB View Download

I've reproduced this issue on Win 10 Pro x64 on two different machines; one with the Intel integrated chipset and one with an Intel i7 paired with an nVidia 1080 Ti. The latter was exhibiting these problems for the last couple of stable version of Chrome, but I've only noticed the trails on my laptop with the latest version, but I could be mistaken, since I don't use it nearly as often as the desktop.

Checked the issue on reported chrome version 64.0.3282.140 and on the latest canary 66.0.3342.0 using Windows 10 Surface Pro with Intel(R) HD Graphics 520.
Still we are unable to see any traces while loading the page. 

@Reporter: As you mentioned in comment#5 that you have noticed the trails only on your laptop, Could you please confirm whether the issue is seen on any other machines with latest chrome versions.

Thanks!

As I've mentioned in the previous comment, in addition to my Spectre x360 laptop, there's my desktop machine with an Intel i7 (no integrated graphics) paired with nVidia 1080 Ti which has been exhibiting this problem (and the diagonal line problem linked in the description) for the last couple of versions (at least 62, I think, maybe even before that).

Unfortunately, I don't have that machine available currently, so I haven't checked version 64.0 on it yet.

Thank you for providing more feedback. Adding requester "vamshi.kommuri@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

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

I'll try to report back with the data from the desktop machine when I have it connected to the net again.

As per comment#9 by reporter adding Needs-Feedback label.

Thanks!

I've had a chance to retest this on the desktop machine with nVidia 1080 Ti and an Intel i7. I see the same thing happening as on the Spectre x360 laptop. Attached is a GIF of the issue.

Also note, I am not using UI scaling on either the desktop or laptop on Windows 10, they're both running at devicePixelRatio == 1.

Deleted: gpu.html 119 KB

gpu.html 119 KB View Download

Deleted: GIF.gif 9.2 KB

	GIF.gif 9.2 KB View Download

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

Reporter, maybe you can perform a bisect yourself, see https://www.chromium.org/developers/bisect-builds-py
It's quite simple:
1) download the script and install python v2
2) run the script:
py bisect-builds.py -a win64 -g 400000 -b 999999
3) observe the bug and input g or b for good/bad status in the script window until the script produces the changelog link
4) copypaste that final block of text here
5) repeat steps 2-3 to ensure you get the correct results

krof.drakula@ Thanks for the feedback.

Tested this issue on Windows 10 and Ubuntu 14.04 on the latest Stable 64.0.3282.186 and Canary 66.0.3352.0 and able to reproduce the issue.
Issue is not observed on Mac OS 10.12.6.

On navigating to the given link, can observe that trails are seen when the rectangles are rotated.
Unable to provide the bisect info as the issue is inconsistent.
Attached is the screen cast for reference.

Also attached is the chrome://gpu details.

Marking this as Untriaged for further updates from Dev team.

Thanks..

Deleted: 809087.webm 1.9 MB

	809087.webm 1.9 MB View Download

Deleted: gpu.html 116 KB

gpu.html 116 KB View Download

I'm definitely not the right owner if this is seen on non-windows.  It should be picked up by the blink triage.

Cannot reproduce this issue on linux desktop.

krof.drakula@: as mentioned in #13, can you please perform a bisect locally? I'll make the issue available per #14.

Due to lack of feedback from OP and lack of reproduction, closing as WontFix

This seems to have been resolved in some of the versions between 65 and 70; I don't see it happening on v70 currently.