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

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


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

android-nexus5X
chromium-rel-mac11

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8971155312643020192

=== Auto-CCing suspected CL author xing.xu@intel.com ===

Hi xing.xu@intel.com, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Xu Xing
  Commit : e3775832e557909d8c24243acb0a5296444a0ce0
  Date   : Sun Aug 13 04:02:52 2017
  Subject: When being copied into another canvas, avoid to check if canvas is dirty

Bisect Details
  Configuration: mac_10_11_perf_bisect
  Benchmark    : blink_perf.canvas
  Metric       : draw-static-webgl-to-hw-accelerated-canvas-2d/draw-static-webgl-to-hw-accelerated-canvas-2d
  Change       : 96.35% | 105148.353689 -> 3833.77296676

Revision             Result                  N
chromium@493985      105148 +- 9264.26       6      good
chromium@493986      103624 +- 6474.34       6      good
chromium@493987      3797.23 +- 215.844      6      bad       <--
chromium@493988      3805.29 +- 236.213      6      bad
chromium@493991      3833.77 +- 62.2441      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.canvas

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8971155312643020192


For feedback, file a bug with component Speed>Bisection

 Issue 755769  has been merged into this issue.

WontFix-ing as this was reverted.