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

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


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

mac-10_12_laptop_low_end-perf

rendering.desktop - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/1717e12ee40000

📍 Found significant differences after each of 2 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/1717e12ee40000

Revert "Remove FlushForDriverCrashWorkaround" by ccameron@chromium.org
https://chromium.googlesource.com/chromium/src/+/e79108ef30139e7809fbada66cac635e39a23c7a
thread_raster_cpu_time_per_frame: 0.4355 → 0.4822 (+0.04676)

cc: Reduce the SolidColorDrawQuad generated by chrome by yiyix@chromium.org
https://chromium.googlesource.com/chromium/src/+/159ad145dd83238fb3d27e709205f9a5cec84be3
thread_raster_cpu_time_per_frame: 0.4783 → 0.5652 (+0.08694)

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

Definitely my patch, well-understood performance/crashiness tradeoff