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

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


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

android-nexus5X

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

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

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

Revision             Result                  N
chromium@528340      691.16 +- 0.650538      2      good
chromium@528436      1617.91 +- 1035.26      5      bad

Please refer to the following doc on diagnosing blink_perf regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/speed/benchmark_harnesses/blink_perf.md

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --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/8957577551031557728


For feedback, file a bug with component Speed>Bisection

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/13c2e4bc840000

Retrying with pinpoint, but this test is really noisy.

📍 Couldn't reproduce a difference.
https://pinpoint-dot-chromeperf.appspot.com/job/13c2e4bc840000

Looks like this is pretty noisy, and went back down.