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

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


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

Win 7 Nvidia GPU Perf

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

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14d1afd3640000

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

Enable automatic flush for canvas context by sunnyps@chromium.org
https://chromium.googlesource.com/chromium/src/+/f3fd321621a946f69068fa5d50dc0c9c505a6bab
40.4 → 46.78 (+6.381)

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

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

This is expected since we started flushing the canvas context more often to mitigate an M69 stable release blocker regression ( issue 880901 ).  I don't see regressions other than tasks_per_frame in the same range that are linked to this CL.

See above comment for WontFix justification.