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

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


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

android-nexus5X

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

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

=== 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_nexus5X_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/background/after_https_www_google_co_uk_hl_en_q_science
  Change       : 7.41% | 17877845.3333 -> 19203413.3333

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/b07af8134668d9c752a45d48003eaf322c03c550..fc2f3e78a68e400ab08ab5f0396fb77428ea4860


Revision             Result                   N
chromium@468625      17877845 +- 2366078      6        good
chromium@468680      16536462 +- 3540534      9        good
chromium@468708      17559845 +- 4717154      14       good
chromium@468716      16204117 +- 2180719      6        good
chromium@468719      17260763 +- 3134506      14       good
chromium@468720      14972587 +- 1811519      6        good
chromium@468721      ---                      ---      build failure
chromium@468722      18240878 +- 1629429      14       bad
chromium@468735      19203413 +- 462666       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 memory.top_10_mobile_stress

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

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


| 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 peter@chromium.org ===

Hi peter@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 : peter
  Commit : ccb33e88ae90c672f98cd24ac631bc92581a199f
  Date   : Tue May 02 19:00:44 2017
  Subject: Rename the DownloadService to DownloadCoreService

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/background/after_https_www_google_co_uk_hl_en_q_science
  Change       : 18.45% | 16212650.6667 -> 19203413.3333

Revision             Result                   N
chromium@468625      16212651 +- 836322       6       good
chromium@468680      16574350 +- 3529910      9       good
chromium@468708      17532075 +- 2061762      6       good
chromium@468722      17347584 +- 2820995      9       good
chromium@468726      17348827 +- 5213350      14      good
chromium@468728      16925525 +- 2091462      6       good
chromium@468729      19692430 +- 3229288      9       bad       <--
chromium@468735      19203413 +- 540136       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 memory.top_10_mobile_stress

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

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


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

I marked that as a bad bisect. Renaming a class does not cause regressions like that.

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