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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgjLmV_AoM


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

android-webview-nexus5X

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

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

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: 7599eb3eee0daef81cef0bdf79294849b5d52e6d
  bad_revision : 59e93059c5418474c88680fb71020bf1fb417d2b

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


Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:v8:effective_size_avg/load_search/load_search_yandex

Revision             Result                  N
chromium@457021      8096599 +- 7776.97      6      good
chromium@457036      8094445 +- 4657.59      6      good
chromium@457043      8092369 +- 4211.43      6      good
chromium@457050      8130087 +- 6620.03      6      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.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 --story-filter=load.search.yandex system_health.memory_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8984591645981929184

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6210299130019840


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : delphick
  Commit : 9d780d130566384f6aff63f127e92340f31a815d
  Date   : Wed Mar 15 10:45:27 2017
  Subject: Ensure the scheduler always changes from UseCase LOADING to NONE.

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:v8:effective_size_avg/load_search/load_search_yandex
  Change       : 0.44% | 8093269.33333 -> 8128818.66667

Revision             Result                  N
chromium@457043      8093269 +- 11245.0      6      good
chromium@457047      8093853 +- 8404.58      6      good
chromium@457048      8093376 +- 1777.55      6      good
chromium@457049      8133615 +- 13642.5      6      bad       <--
chromium@457050      8128819 +- 15078.5      6      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.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 --story-filter=load.search.yandex system_health.memory_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8984571529067596480

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6371661588201472


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!