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

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


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

android-webview-nexus6

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

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

Hi treib@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 : treib
  Commit : 440d4dd2c735245ec61a12a1bb7b011e4130c655
  Date   : Tue May 16 07:21:45 2017
  Subject: NewTabUI: Remove not-OffTheRecord case, since it's not used anymore

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/browse_social/browse_social_twitter
  Change       : 20.74% | 5635705.90476 -> 4466883.04762

Revision             Result                   N
chromium@472033      5635706 +- 18313796      21      good
chromium@472034      5184853 +- 162133        6       bad       <--
chromium@472035      5057877 +- 191456        6       bad
chromium@472037      4957525 +- 192178        6       bad
chromium@472040      4818261 +- 95123.7       6       bad
chromium@472047      5154133 +- 182598        6       bad
chromium@472061      5027840 +- 176152        6       bad
chromium@472089      4932267 +- 156016        6       bad
chromium@472145      4466883 +- 1327793       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 --story-filter=browse.social.twitter system_health.memory_mobile

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

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


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

That's almost certainly not mine. That CL removed some long-dead code, which was never even used on Android in the first place.

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

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

Hi eugenebut@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 : eugenebut
  Commit : 05c0673d05e9338eafd256a55f9ee1b6f1281c68
  Date   : Mon May 15 21:09:16 2017
  Subject: Updated comments for webViewLoadingStateDidChange.

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/browse_social/browse_social_twitter
  Change       : 73.67% | 11648568.8889 -> 4104874.66667

Revision             Result                    N
chromium@471823      11648569 +- 16715029      9      good
chromium@471864      3894841 +- 213420         9      good
chromium@471884      3991780 +- 192739         9      good
chromium@471894      4153344 +- 295026         9      good
chromium@471899      4345856 +- 268967         9      good
chromium@471900      4765696 +- 78307.6        6      bad       <--
chromium@471901      4618923 +- 113166         6      bad
chromium@471902      4515157 +- 148777         6      bad
chromium@471904      5043996 +- 11577049       9      bad
chromium@471984      3841365 +- 74106.3        6      bad
chromium@472145      4104875 +- 83072.4        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.social.twitter system_health.memory_mobile

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

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


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

My CL updates iOS comments, there is no way it can regress Android memory usage.

This alert was found before M-60 branched. Closing as WontFix as this is believed to either be invalid or non-reproducible.