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

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


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

android-nexus6

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:java_heap:effective_size_avg/browse_news/browse_news_nytimes
  Change       : 3.61% | 114618658.857 -> 117531770.0

Suspected Commit Range
  5 commits in range
  https://chromium.googlesource.com/chromium/src/+log/d3f393cf3116d1f44b5a41b0e12165747f253c4c..0d01f9fe710dfbe680f317621a617e383422e14d


Revision             Result                     N
chromium@455041      114618659 +- 10713996      14       good
chromium@455042      ---                        ---      build failure
chromium@455043      ---                        ---      build failure
chromium@455044      ---                        ---      build failure
chromium@455045      ---                        ---      build failure
chromium@455046      115794139 +- 13754173      14       bad
chromium@455051      117531770 +- 9908582       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.nytimes system_health.memory_mobile

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

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


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

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

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

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:java_heap:effective_size_avg/browse_news/browse_news_nytimes

Revision             Result                     N
chromium@455042      115782306 +- 16798095      21      good
chromium@455046      114637298 +- 13088858      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-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.nytimes system_health.memory_mobile

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

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


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

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