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

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


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

android-webview-nexus5X

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Error: TIMEOUT

The bisect was able to narrow the range, you can try running with:
  good_revision: 9a4a1121fae26a1727728888a41975bc15e3e62f
  bad_revision : 1295f7b381ba68280d4143cc638f3928e4128d72

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : blink_perf.canvas
  Metric       : draw-video-to-hw-accelerated-canvas-2d/draw-video-to-hw-accelerated-canvas-2d
  Change       : 99.25% | 107745.335412 -> 805.561735643

Revision             Result                  N
chromium@484795      107745 +- 116818        6      good
chromium@484831      117243 +- 137480        6      good
chromium@484851      120266 +- 49300.1       6      good
chromium@484866      805.562 +- 210.433      6      bad

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


For feedback, file a bug with component Speed>Bisection

Looks like this is bimodal, returned to expected values.