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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrObRuAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgzOXx7wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgzKGe7ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgzKGergsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrJigoQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgzIH0_gsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrJiTtAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgzL-SrQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrPLgsQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrJiFpQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrJiFpQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrKyfqQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrIXruAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrKyfqQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgrKzLsAoM


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

android-webview-nexus6

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

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

Hi msarda@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 : msarda
  Commit : d625c6d1708edd48bada92dde69fc4905dcf1dd2
  Date   : Wed Mar 22 13:06:30 2017
  Subject: Remove finch experiments for NewProfileManagement.

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/background/after_http_www_baidu_com_s_word_google
  Change       : 7.27% | 1660586.66667 -> 1781248.0

Revision             Result                  N
chromium@458725      1660587 +- 150796       9      good
chromium@458726      1789269 +- 3739.12      6      bad       <--
chromium@458727      1787221 +- 4729.65      6      bad
chromium@458728      1787221 +- 4729.65      6      bad
chromium@458731      1787904 +- 5016.55      6      bad
chromium@458737      1773568 +- 70231.8      9      bad
chromium@458749      1781248 +- 47673.8      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-webview --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/8984291289798383344

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


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

My CL is a removal of dead code, it should have no impact on performance (it is basically).

I think there was probably something flaky in the bisect.

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