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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg3sn--AoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7veR-AkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7r-tqAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnsGo9AkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7ubKlQgM


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

android-webview-nexus6

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/foreground/http_en_m_wikipedia_org_wiki_Science

Revision             Result                   N
chromium@483108      50078554 +- 1124948      21      good
chromium@483148      50097522 +- 657685       21      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

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

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


For feedback, file a bug with component Speed>Bisection

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

=== Auto-CCing suspected CL author kenrb@chromium.org ===

Hi kenrb@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : kenrb
  Commit : aaef60b215683bef8c612aa8b19f39ca31c46438
  Date   : Wed Jun 28 18:43:06 2017
  Subject: Partial revert of Remove AreCrossProcessFramesPossible on Android.

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/foreground/http_en_m_wikipedia_org_wiki_Science
  Change       : 1.66% | 49084834.6667 -> 49898744.0

Revision             Result                  N
chromium@483010      49084835 +- 594764      6       good
chromium@483045      49349027 +- 681276      9       good
chromium@483062      49391718 +- 963692      14      good
chromium@483071      49202936 +- 762937      6       good
chromium@483075      49428330 +- 933817      9       good
chromium@483077      49514915 +- 225887      6       good
chromium@483078      50118904 +- 516364      6       bad       <--
chromium@483079      49826780 +- 538279      9       bad
chromium@483148      49898744 +- 207909      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

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

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


For feedback, file a bug with component Speed>Bisection

The blamed CL was a revert of an earlier change, which presumably must have caused a memory improvement (I have had other bugs assigned to me suggesting that this is the case). Closing, since there is nothing to do for this.