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

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


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

android-nexus5X

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

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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/foreground/http_m_youtube_com_results_q_science

Revision             Result                   N
chromium@468687      16020529 +- 4933166      21      good
chromium@468774      17023269 +- 3241233      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/8980426377801429632

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


| 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/8980330006403553728

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

Hi dschuyler@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 : dschuyler
  Commit : f83540958fb0ffff1080a759eb3e7b2a06e32902
  Date   : Tue May 02 19:05:54 2017
  Subject: [MD settings] clear incognito only checkbox

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/foreground/http_m_youtube_com_results_q_science
  Change       : 7.64% | 15636382.4762 -> 16831707.4286

Revision             Result                   N
chromium@468687      15636382 +- 4032477      21      good
chromium@468731      15469080 +- 2931565      21      good
chromium@468732      17193301 +- 377129       6       bad       <--
chromium@468733      17387520 +- 173289       6       bad
chromium@468734      17235115 +- 177678       6       bad
chromium@468737      17190912 +- 281527       6       bad
chromium@468742      17346560 +- 407863       6       bad
chromium@468753      17279488 +- 149523       6       bad
chromium@468774      16831707 +- 3116259      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/8980426387369136496

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


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

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

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/foreground/http_m_youtube_com_results_q_science

Revision             Result                   N
chromium@468687      15953432 +- 4903676      21      good
chromium@468774      16863817 +- 3857977      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/8980330006403553728

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


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

Reported as a bad bisect since I don't see how f83540958fb0ffff1080a759eb3e7b2a06e32902 could be the culprit (please let me know if you still believe it is the culprit). 

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