Tested this issue on Windows-10 using chrome latest stable M55-55.0.2883.87 by following steps mentioned in the original comment. Observed the FPS meter of chrome shows 30 frames per second in dev tools. 

Sounds like this issue is specific to AMD hardware, Requesting someone from MTV folks to look in to this issue for further triaging.

Thanks!

Geoff, do you have an AMD GPU in the office and if so could you triage this quickly? It sounds like a potential problem with ANGLE. Let's also test Canary in case it's a problem that's already been fixed.

Thanks.

Was able to reproduce on an AMD system.  Got about 30 FPS on bad Chrome versions and about 60 on good.

It's fixed in Canary so I did a bisect-builds and narrowed down the fix to this ANGLE roll: https://chromium.googlesource.com/chromium/src/+/b5de482ad9cc882bf3ef9a73f3d75953a3350c44 which contains this CL: https://chromium.googlesource.com/angle/angle.git/+/408293f8a4dfa129eb47df996cc6881cefb9c9c2 which is a fix for an AMD workaround.

We could try to merge this back to 56.

Thanks Geoff for tracking that down. Let's request a merge back. Since that bug didn't have a Chromium issue, not sure exactly how this works for tracking purposes.

This bug requires manual review: We are only 10 days from stable.
Please contact the milestone owner if you have questions.
Owners: amineer@(clank), cmasso@(bling), gkihumba@(cros), bustamante@(desktop)

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

Marking fixed as per the merge request guidelines.

We're too close to stable for this change to make sense, typically we're only taking high severity security/crash fixes right now, and this CL is pretty large.  

I'd like to wait until M-57, if you think this should still qualify.  Please add the "Merge-Review-56" label with a justification and we'll review it.