Thanks for filing the issue!

Unable to reproduce the issue on reported chrome version 71.0.3578.98 using Windows 10 with the below mentioned steps.
1. Launched Chrome
2. Navigated to a random webpage.
3. Tried dragging the window.
In the process we didn't observe any artifact(s).

@Reporter: Could you please let us know if this is happening with every window/webpage or is this specific to any site. Any other inputs from your end may help us to triage this further in a better way. 

It doesn't matter what website it is. I does it with a single chrome tab on the google page. I made a little video to demonstrate. This is a fresh restart of one of the windows 7 vm's doing it. There is a single Chrome tab open and the task manager window. Dragging over chrome produces artifacts until chrome is clicked on. Then I show the same over IE no artifacts. Then I show a second chrome tab over the first chrome tab, again artifacts.

It is to big to upload so I put on dropbox.

https://www.dropbox.com/s/1u76lvp8krh6ut1/2019-01-17%2008.09.33.mov?dl=0  

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

Our organization is experiencing the same issue.  We use Citrix Xendesktop 7.6 and our desktops are statically assigned, running Windows 7 Enterprise. Our first instance occurred 1/11 and this last week many more people began experiencing the problem.  

One consistent finding is the artifacting is only happening when Chrome is in full screen mode.  It does not occur when the Chrome window is any other size.  Also, the first time you sign on to the desktop with a new profile and launch Chrome, the issue does not occur, even when in full screen mode.  But close Chrome then reopen it and the artifacting occurs (again, only when in full screen mode). 

I have found this happens among all Windows profiles, existing and new so it's not a profile problem.  I have been able to reproduce the issue with Chrome 71.0.3578.98 (all users currently running this version) and on one desktop I downgraded to ver. 71.0.3578.80 and the issue occurred there too.  I then downgraded to 69.0.3497.92 and the issue did not occur.  Went back to ver. 71.0.3578.98 and the issue returned.  I only did this downgrading on one desktop so far but plan to do this on more systems to see if it's consistent or not.

I too have tried disabling hardware acceleration in chrome but the issue occurs regardless.  No recent Windows updates have been run, only recent update was Firefox to ver. 64.

We do have some users that are not having the problem.  Not sure why as their desktops come from the same base image and run the same software, get the same updates pushed to them, and they are running the current version of Chrome.  I plan on looking at these desktops to see what is different and try to make the issue occur on them (maybe they don't run Chrome full screen?).  It could be the problem will eventually occur for them as the issue seems to be slowly spreading.   Will do some additional tests and report my findings here.