Are you able to provide a screen recording of the issue?

https://youtu.be/UFyULak4-Rk
https://youtu.be/GazCKihEBwY
When I use screen recording, the problem does not occur, so I can only use the phone to shoot the screen (the sound has nothing to do with the content). For clarity, I adjusted the DPI to 175% (any DPI will have a problem). Focus on the location of the screen border, when the mouse on the link, the window will be moved down a few pixels, the mouse left the link window recovery.
Then I turn off the hardware acceleration, the browser no longer jitter
Other points: when the browser window is not the most large, or occlusion in the browser window at the top, the browser will not go wrong

I can see you problem in the video. The entire Chrome window contents are moving, which is very odd. It also means it is not a Blink painting bug.

For those following along, the first video from comment #3 shows the effect, particular when looking at the Chrome tabs labels and user indicator.

Guessing labels.

Unable to reproduce the scenario on windows 10 with chrome version #55.0.2883.75.

Reproduced the scenario as per comment #0, observed that chrome window contents are not moving.

Attaching the screencast for your reference, please look into it and let us know your observations.

Deleted: Issue 672448.mp4 1.8 MB

	Issue 672448.mp4 1.8 MB View Download

Please note that using the software to record the screen, or the browser window is blocked can not be reproduced!
I do not know how to reproduce on other computers, if you have a good idea, I can test according to your proposal.
I guess maybe a specific version of windows10 will be a problem, this is my online search to the same situation with me, some people say that the system upgrade to windows 10 1607 to this Kind of situation
https://translate.google.com/translate?hl=zh-TW&sl=zh-CN&tl=en&u=https%3A%2F%2Fwww.baidu.com%2Fs%3Fie%3DUTF-8%26wd%3Dwin10%20Chrome%20%E6%8A%96%E5%8A%A8
※I found new information. When the browser uses a small window, a black pixel appears on the right side of the window, and Chrome will jitter. Black pixels disappear after scaling, and Chrome does not shake.
https://youtu.be/mGMvBXgbyDk
https://youtu.be/VcQkKbPHl8w
https://youtu.be/Ja0FNmWxcug

Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" for another review and adding "Needs-Review" label for tracking.

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

CCing windows gpu folks

 Issue 684544  has been merged into this issue.

 Issue 684544  suggests that this could be due to having scaling in Windows turned on

 Issue 648081  has been merged into this issue.

I'm also still getting this bug with chrome version 56.0.2924.87 (64-bit).  Also, on Windows 10 64-bit with Anniversary Update. NVidia and Intel graphics drivers are up-to-date.

  This bug only shows up when using a DPI scaling that is above 100%. This setting is provided by Windows UI Settings>Display>"Change the size of text, apps, and other items"

The only thing I have found that will remove this bug is either reduce the DPI scaling back to 100% (Not a solution) or turn off hardware acceleration in chrome settings (Also not a solution).

Also forgot: bug only shows up when window is maximized.

To all of you that still are experiencing this issue and have an Intel Graphics Card.

I have updated to the latest Intel drivers (21.20.16.4590) From 1/18/2017 and it solved the issue for me! Finally!

http://www.intel.com/content/www/us/en/support/detect.html

Thanks #18
I have downloaded the latest Intel Drivers and it's finally resolved!
So this bug only appears if:
1. Windows 10 Anniversary Update (1607)
2. Some versions of Intel GPU drivers
3. Hardware acceleration is enabled
4. Window is maximized
5. High DPI (e.g 125%)

Could the person from comment #17 try updating the driver and see if the issue persists?

I'm inclined to close this bug now there are reports that issue no longer exists w/ driver update.

Cleaning up "Needs-Review" label as we are not using this label for triage. Ref  bug 684919 

Closing due to lack of feedback over 31 days.  Please re-open if issue still occurs and more information can be added.

 Issue 716028  has been merged into this issue.