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

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


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

android-webview-nexus5X

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

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

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : blink_perf.bindings
  Metric       : id-getter/id-getter

Revision             Result                  N
chromium@511112      151.447 +- 31.1138      21      good
chromium@511161      124.118 +- 200.745      21      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-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests blink_perf.bindings

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

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


For feedback, file a bug with component Speed>Bisection

In all the graphs, this seems to be a return to normal levels after a blip. Bisect can't repro.