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

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


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

android-webview-nexus5X

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

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

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

Hi jbudorick@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 : John Budorick
  Commit : 1e16afc846438637e7be1dc19e02ccea8bc23685
  Date   : Thu Jun 15 18:37:04 2017
  Subject: [android] 2 shards & 20 minute timeout for unit_tests on N Phone Tester.

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/load_news/load_news_irctc
  Change       : 0.55% | 10075794.2857 -> 10087424.0

Revision             Result                   N
chromium@479753      10075794 +- 155132       14      good
chromium@479761      9961472 +- 15325.8       6       good
chromium@479764      9960789 +- 24174.5       6       good
chromium@479765      9952597 +- 28030.9       6       good
chromium@479766      10109147 +- 225095       14      bad       <--
chromium@479778      10144085 +- 107190       6       bad
chromium@479803      10087424 +- 37540.5      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.news.irctc system_health.memory_mobile

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

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


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

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

Hi aleventhal@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 : Aaron Leventhal
  Commit : 538180be326371b71af05d3ef299af5ce34e1d58
  Date   : Thu Jun 15 19:26:46 2017
  Subject: Add blink input-range test

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/load_news/load_news_irctc
  Change       : 0.82% | 10155235.5556 -> 10072405.3333

Revision             Result                   N
chromium@479753      10155236 +- 165177       9       good
chromium@479778      10106441 +- 192870       14      good
chromium@479779      9925291 +- 13481.6       6       bad       <--
chromium@479780      9932800 +- 19211.9       6       bad
chromium@479781      9935531 +- 9459.31       6       bad
chromium@479784      10027593 +- 340451       21      bad
chromium@479791      10091520 +- 229321       14      bad
chromium@479803      10072405 +- 92319.2      9       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.news.irctc system_health.memory_mobile

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

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


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

These CLs really don't look related at all.

java_heap is not being very bisectable (issue 724032) :(

Anyway, this looks like a land/revert with numbers coming back to baseline, so fine to WontFix