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

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


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

android-nexus5

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

=== 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_nexus5_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_tools/load_tools_stackoverflow
  Change       : 1.19% | 4749693.33333 -> 4806231.33333

Suspected Commit Range
  5 commits in range
  https://chromium.googlesource.com/chromium/src/+log/ee71e66f483b63c57c67fe350722a049579bd2ec..214b3a27cc09cc76ba9b24a2eac7e41478cda770


Revision             Result                  N
chromium@442254      4749693 +- 66954.5      9        good
chromium@442300      4764133 +- 107070       14       good
chromium@442305      4756389 +- 24246.3      6        good
chromium@442308      4758699 +- 61329.8      14       good
chromium@442309      4765389 +- 132986       21       good
chromium@442310      ---                     ---      build failure
chromium@442311      ---                     ---      build failure
chromium@442312      ---                     ---      build failure
chromium@442313      ---                     ---      build failure
chromium@442314      4799490 +- 77068.6      14       bad
chromium@442323      4779945 +- 82444.6      14       bad
chromium@442345      4793942 +- 71975.5      9        bad
chromium@442435      4806231 +- 70089.9      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=load.tools.stackoverflow system_health.memory_mobile

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

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


| 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 Tests>AutoBisect.  Thank you!

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