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

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


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

android-webview-nexus6

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

=== 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    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/browse_news/browse_news_globo


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=browse.news.globo system_health.memory_mobile

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

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


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

=== 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    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/browse_news/browse_news_globo
  Change       : 18.78% | 104148594.667 -> 123703908.0

Revision             Result                    N
chromium@468211      104148595 +- 4096116      6      good
chromium@468219      104729753 +- 4239936      6      good
chromium@468221      105488620 +- 5786540      6      good
chromium@468222      104188701 +- 3045975      6      good
chromium@468223      124572767 +- 4072018      6      bad       <--
chromium@468227      123703908 +- 7718281      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=browse.news.globo system_health.memory_mobile

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

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


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