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

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


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

android-webview-nexus6

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

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

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


Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/background/after_http_yandex_ru_touchsearch_text_science


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 memory.top_10_mobile_stress

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

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


| 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/8980751595475977776

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

Suspected Commit
  Author : avayvod
  Commit : 77db41b769602da7ccc0106c285490f149fe343d
  Date   : Sat Apr 29 04:09:14 2017
  Subject: Remove the explicit dependency between HTMLMediaElement and MediaControls

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/background/after_http_yandex_ru_touchsearch_text_science
  Change       : 3.72% | 105863597.333 -> 109805826.667

Revision             Result                    N
chromium@468222      105863597 +- 1087683      6      good
chromium@468223      110859181 +- 760467       6      bad       <--
chromium@468224      110274477 +- 1257963      6      bad
chromium@468226      109805827 +- 1189333      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 memory.top_10_mobile_stress

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

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


| 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!

Blocking on crbug.com/713747 for busted android_webview_nexus6_aosp_perf_bisect.