Unable to reproduce the issue using Chrome Remote Desktop 52.0.2743.48 and Stable 54.0.2840.59 on Ubuntu 14.04 and accessing from Windows 10 machine.

I was on my Goobuntu machine. I think it matters here. I get 100% even on the page with My Computers when I click Refresh.

See if you get the same problem with https://chrome.google.com/webstore/detail/chrome-key-event-tester/amndppkiecbdmiaihgbicalhabkkhhpk. Before you make a connection, CRD is not doing much, but it does pre-load a NaCl plugin. The app I liked to does too, so it might shed some light on what's going on.

Durga : As per #3, can you give a try using Ubuntu.
vasilii@ : Can you please confirm whether the issue exist using pervious stable- 53.0.2785.143.

Tried the issue making Ubuntu 14.04 as host and Win 10 as Client using 54.0.2840.59 and vice versa, could not reproduce it.

Chrome key event tester has the same issue.
Tested as well on 53.0.2785.143 (Official Build) (64-bit) with Chrome Key Event Tester and remote desktop. The 100% load isn't observed.

jamiewalch@ could you find someone from your team for further triaging and investigation. vasilii@ please provide chrome://gpu information.

Tagging with blocker label in case of any escalations in future.As per #8, the issue persist on previous stable release. 

On M53 there was no such an issue. Today I can't reproduce it on 54 too. Probably it's something local on my machine.

It doesn't look like this is related to Chromoting and I'm not sure we can reproduce the issue to help track it down.

closing since the issue is resolved.Please feel free to reopen if needed.

I have the problem again today. It's enough to move mouse over UI elements of the remote desktop app to get high load.
chrome://gpu:
https://docs.google.com/a/google.com/document/d/1MBy_3AAAy65wyew-QoxVzXx7vGIjEsEdzUfN93sGTDU/edit?usp=sharing

Would you mind updating to latest chrome stable version - 54.0.2840.71 and update the thread. 
Meanwhile looping to GPU experts in our team for further inputs from chrome://gpu information.

NVIDIA's 361.42 driver is known to have bugs. I suggest you update to the 367.35 driver which is easily available via synaptic or other package managers.

Updated to Nvidia 367 and don't see the issue today.

Thanks for testing. Closing as WontFix (driver bug). There was a thread on goobuntu-discuss about this poor choice of driver; I suggest you follow up on it.