Bisect Range:
===================
Last Good Build: 66.0.3349.0
First Bad Build: 66.0.3350.0

Note: Facing an exception error while running gsutil command. 
Attaching the screenshots of the Good and Bad behaviour for reference.

Thanks! 

Deleted: Good-813463.PNG 43.5 KB

	Good-813463.PNG 43.5 KB View Download

Deleted: Bad-813463.PNG 39.7 KB

	Bad-813463.PNG 39.7 KB View Download

Change log:
=============
https://chromium.googlesource.com/chromium/src/+/21620f905fe7cf72d23c16e170e3f9c8018ed0a1

Suspecting the same.
Review URL:  https://chromium-review.googlesource.com/922454

@malaykeshav: Please help in re-assigning it to others if not related to your change. 

Note: Adding RB-stable as this is a recent regression. Currently we don't have proper set-up for tool bisect in HighDPI machine, hence provided with manual Change Log.

Thanks!

The scale on clip path only needs to be applied when Pixel Canvas is enabled. Which is not yet the case for Windows. 
Uploading a patch.

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/51706e1cfa0c8f3b26be99a7d4de4ffaf908f673

commit 51706e1cfa0c8f3b26be99a7d4de4ffaf908f673
Author: Malay Keshav <malaykeshav@chromium.org>
Date: Tue Feb 20 20:56:58 2018

Use paint recording scale factor instead of device scale factor

The paint recording scale factor is set to 1 when pixel canvas is
disabled. We cannot use the value of PaintContext::device_scale_factor
for the recording scale factor in such cases.

Bug:  813463 
Change-Id: If51bfde2e271ce863cf3971016ee6347cbce592a
Component: Tabs, Clipping, Scaling
Reviewed-on: https://chromium-review.googlesource.com/927182
Reviewed-by: Peter Kasting <pkasting@chromium.org>
Commit-Queue: Malay Keshav <malaykeshav@chromium.org>
Cr-Commit-Position: refs/heads/master@{#537876}
[modify] https://crrev.com/51706e1cfa0c8f3b26be99a7d4de4ffaf908f673/chrome/browser/ui/views/tabs/tab.cc

Verified the fix on Windows 10 using latest chrome version #66.0.3352.0 as per the comment #0.
Attaching screen shot for reference.
Observed that the text and favicon rendered properly on the tabs without any crop.
Hence, the fix is working as expected.
Note: Able to reproduce the issue on reported chrome version. 
Adding the verified labels.

Thanks...!!

 Issue 816553  has been merged into this issue.