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

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


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

android-nexus7v2

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

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

=== 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_nexus7_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/foreground/http_yandex_ru_touchsearch_text_science
  Change       : 12.42% | 62971904.0 -> 71408298.6667

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/1547f4c5289b094a0d0487e6c54297cede4d5db7..9888c32790d9934ce4a4446349c9a691536561cd


Revision             Result                    N
chromium@468953      62971904 +- 153696        6        good
chromium@468984      63004672 +- 844372        6        good
chromium@469000      63019691 +- 239957        9        good
chromium@469004      63004672 +- 227023        6        good
chromium@469006      63401691 +- 1580551       14       good
chromium@469007      ---                       ---      build failure
chromium@469008      69881271 +- 15259995      14       bad
chromium@469015      71408299 +- 8687144       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-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.top_10_mobile

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

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


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

Hi lpromero@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 : lpromero
  Commit : d60ed8e2a67ef19c3cef5596938364dea1342b14
  Date   : Wed May 03 15:22:13 2017
  Subject: Remove code in subclasses already performed by the base class.

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/foreground/http_yandex_ru_touchsearch_text_science
  Change       : 9.16% | 63168121.9048 -> 68954697.1429

Revision             Result                    N
chromium@468953      63168122 +- 1623349       21      good
chromium@468969      63004672 +- 160530        9       good
chromium@468973      63062926 +- 617879        9       good
chromium@468975      63033799 +- 294710        9       good
chromium@468976      62982827 +- 177472        6       good
chromium@468977      63826603 +- 902286        6       bad       <--
chromium@468984      63725373 +- 2266806       21      bad
chromium@469015      68954697 +- 16316031      14      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

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

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


| 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 bisect is wrong. My CL only touched iOS code. I reported the bad bisect with the link above.

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to continue

Bisect was stopped because a commit couldn't be classified as either
good or bad.


Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/foreground/http_yandex_ru_touchsearch_text_science

Revision             Result                    N
chromium@468800      63164806 +- 1461301       21      good
chromium@468908      63424414 +- 3465534       21      unknown
chromium@469015      68403005 +- 21187968      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 memory.top_10_mobile

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

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


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