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

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


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

chromium-rel-mac-retina

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : blink_perf.canvas
  Metric       : toBlob_duration/toBlob_duration

Revision             Result                  N
chromium@501652      219.23 +- 17.7806       21      good
chromium@501751      218.523 +- 14.0507      21      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/8967712369622884448


For feedback, file a bug with component Speed>Bisection

Seems to be just a regression of an earlier improvement (@494106). Also the metric has improved since then. Closing it given that and the above no result bisect.