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

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


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

android-nexus5X

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

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

Hi jam@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 : jam
  Commit : 2d87f324bbce487b2615d3c3d968ab19414ad811
  Date   : Fri Jun 09 18:06:28 2017
  Subject: Update Network Service layout test expectations.

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:java_heap:effective_size_avg/browse_news/browse_news_qq
  Change       : 0.11% | 64822713.6667 -> 64896022.6667

Revision             Result                   N
chromium@478277      64822714 +- 45659.5      6       good
chromium@478331      64815543 +- 145484       14      good
chromium@478332      65279618 +- 203772       6       bad       <--
chromium@478333      65185751 +- 224405       6       bad
chromium@478335      65103196 +- 66973.8      6       bad
chromium@478338      65056727 +- 85953.3      6       bad
chromium@478344      65014445 +- 247696       6       bad
chromium@478357      65096062 +- 344490       6       bad
chromium@478385      64831394 +- 200379       14      bad
chromium@478492      64896023 +- 113419       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-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.qq system_health.memory_mobile

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

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


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

Metrics recovered around:
http://test-results.appspot.com/revision_range?start=480380&end=480528

Looks like a land-revert pattern?

The metric didn't go back quite as low as before the regression, but it looks like there is an overall upward trend in the graph. So, I agree it looks like a land-revert.