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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgxOvQsQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghPyllgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgxLDTkQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDghPOsiQgM


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

android-nexus5X
android-nexus7v2
android-webview-nexus5X
android-webview-nexus6

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

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

Suspected Commit
  Author : yhirano
  Commit : 865407349e3755b33d6db5642501f88c8fb7784d
  Date   : Fri Feb 24 14:43:30 2017
  Subject: Do not reuse a loading resource associated with another fetcher

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/load_social/load_social_tumblr
  Change       : 10.10% | 106792037.333 -> 117582949.333

Revision             Result                    N
chromium@452819      106792037 +- 998091       6      good
chromium@452822      106638267 +- 606759       6      good
chromium@452823      117831440 +- 2695273      6      bad       <--
chromium@452824      118104165 +- 937124       6      bad
chromium@452828      117506661 +- 3968284      6      bad
chromium@452838      117727675 +- 3304507      6      bad
chromium@452857      117582949 +- 1380023      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.social.tumblr system_health.memory_mobile

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

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


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