Able to reproduce the issue on Windows 7,Ubuntu 14.04 using latest Canary #62.0.3197.0 dev

Manual Bisect info:
------------------
Good Build:62.0.3196.0 dev
Bad Build :62.0.3197.0 dev

Using per-revision bisect providing the bisect results:

You are probably looking for a change made after 497600 (known good), but no later than 497601 (first known bad).
CHANGELOG URL:
 https://chromium.googlesource.com/chromium/src/+log/c196e5998015478a7a8955643dcad0ba8b9ad62c..f5fb596736f90c3e00f8f2aa70daea555e8bb664

Suspecting: https://chromium.googlesource.com/chromium/src/+/f5fb596736f90c3e00f8f2aa70daea555e8bb664
Review-Url: https://chromium-review.googlesource.com/633851

skobes@:Could you please take a look into this issue and reassign if this issue is not related to your change.

Thanks..!!

Issue is reproducible on the latest Mac chrome canary: 62.0.3198.0 as well.

 Issue 759805  has been merged into this issue.

 Issue 759429  has been merged into this issue.

Patch up: http://crrev.com/c/639011

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

commit 14e906a67f9ae321535d917a486c14a17b7ea3cb
Author: Steve Kobes <skobes@chromium.org>
Date: Wed Aug 30 00:31:29 2017

Fix repaint of scrolling contents layer on layout overflow change.

If a composited scroller with a solid-color background has its layout overflow
rect resized, the scrolling contents layer needs a paint invalidation.

This broke in r497601, which made the scrolling contents layer's invalidation
conditional on BackgroundGeometryDependsOnLayoutOverflowRect.

Bug:  759436 ,  734187 
Cq-Include-Trybots: master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I6dd689dc6766bf76cc4c6d7a3915e0cd2202cda6
Reviewed-on: https://chromium-review.googlesource.com/639011
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Commit-Queue: Steve Kobes <skobes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#498305}
[modify] https://crrev.com/14e906a67f9ae321535d917a486c14a17b7ea3cb/third_party/WebKit/Source/core/paint/BoxPaintInvalidator.cpp
[modify] https://crrev.com/14e906a67f9ae321535d917a486c14a17b7ea3cb/third_party/WebKit/Source/core/paint/BoxPaintInvalidatorTest.cpp

This seems to be working fine on the latest canary(62.0.3200.0) on Windows-10, Mac OS 10.12.6 and Linux Ubuntu 14.04 as per the test steps in C#1.

skobes@: If there is no further work to be done here, shall we tag this as Fixed?

Issue 760726 has been merged into this issue.

 Issue 760397  has been merged into this issue.

 Issue 761219  has been merged into this issue.

 Issue 760645  has been merged into this issue.

 Issue 762348  has been merged into this issue.

 Issue 762522  has been merged into this issue.

 Issue 762458  has been merged into this issue.

I'm getting a problem that looks just like this, but I'm running beta: currently on 61.0.3163.117/9765.79.0 on samus, but it also reproed on the previous build.

Happened periodically to some random tabs (mostly Inbox); turned on force GPU rasterisation in chrome://flags at dcastagna@'s suggestion and all that did was change the shape of the corruption/blank tiles to be the whole width of the tab when it occurs. Screenshot attached of an example with forced rasterisation; didn't capture one of the previous corruption but it looked the same as the other examples in the bugs duped to this one.

Did this bug definitely only regress in 62?

Deleted: Screenshot 2017-10-09 at 4.22.10 PM.png 166 KB

	Screenshot 2017-10-09 at 4.22.10 PM.png 166 KB View Download

Yes, this bug definitely regressed at r497601 which is after the M61 branch at r488528.  Please file a new bug for your issue.

ChromeOS 9901.66.0, 62.0.3202.82