All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=821100

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=6dfe2ff6fce59c635ead3bb24cdd6ab7842e0fec81d2ffa5e7e440871a520d77


Bot(s) for this bug's original alert(s):

win-high-dpi

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/11ffb2c6440000

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/11ffb2c6440000

Surface synchronization: Don't block on the top level renderer on Windows by fsamuel@chromium.org
https://chromium.googlesource.com/chromium/src/+/3879527a58c5df0e54fa035bfa5bcba9abca92a0

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

We won't address this in the short term. I think it's generally preferable to gutter the page's background color, then block UI during resize and get a black gutter.

I think this has mostly been addressed but we've also changed the way we measure timeToFirstMeaningfulPaint so it's hard to do an apples to apples comparison. I'm marking as WontFix.