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

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


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

android-webview-nexus5X
android-webview-nexus6
win-high-dpi

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : speedometer
  Metric       : VanillaJS-TodoMVC/VanillaJS-TodoMVC


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

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

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


For feedback, file a bug with component Speed>Bisection

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

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

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

Please try rerunning the bisect.


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


Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : speedometer
  Metric       : jQuery-TodoMVC/jQuery-TodoMVC

Revision             Result                  N
chromium@519842      2943.83 +- 130.598      14      good
chromium@520202      3169.82 +- 144.058      14      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 speedometer

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

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


For feedback, file a bug with component Speed>Bisection

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

Please try rerunning the bisect.


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


Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : speedometer
  Metric       : RunsPerMinute/RunsPerMinute
  Change       : 2.96% | 28.2742857143 -> 27.41

Revision             Result                  N
chromium@519842      28.2743 +- 0.70338      14      good
chromium@520202      27.41 +- 0.462817       14      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 speedometer

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

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


For feedback, file a bug with component Speed>Bisection

Looks like the bot is having trouble finding another working build before hitting the 24 hour limit.

This regression has been open for half a year. It's not very actionable and the regression has been in all Chrome user's hands for months.