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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=cb4c819f25cc1aa5a4c9896d8a41456595db903cdf9cd42902036b5368308089


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

android-webview-nexus6

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

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

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:malloc:effective_size_avg/background/after_http_m_intl_taobao_com_group_purchase_html

Revision             Result                   N
chromium@488644      34658807 +- 1555083      21      good
chromium@488797      34843654 +- 1433243      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-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.top_10_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8973181283297945152


For feedback, file a bug with component Speed>Bisection

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

Re-bisecting on cleaner signal

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Ulan Degenbaev
  Commit : 176a2b24fb23a0c9a3bc9eec27f6445dbfa5ab27
  Date   : Wed Jul 19 13:04:47 2017
  Subject: [heap] Reland "[heap] Allow a minimum semi-space size of 512K."

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/foreground/http_search_yahoo_com_search__ylt_p_google
  Change       : 1.50% | 5082244.0 -> 5158663.33333

Revision                           Result                  N
chromium@488742                    5082244 +- 34347.2      6      good
chromium@488745                    5085117 +- 29513.6      6      good
chromium@488745,v8@ae9a2d38f3      5084044 +- 42763.2      6      good
chromium@488745,v8@91c1a81d0e      5085400 +- 27732.0      6      good
chromium@488745,v8@bb29f9a4d6      5089845 +- 28443.8      6      good
chromium@488745,v8@176a2b24fb      5179975 +- 53276.7      6      bad       <--
chromium@488745,v8@7cfd0c249e      5180589 +- 87964.4      6      bad
chromium@488745,v8@b23b8c088c      5149384 +- 57155.1      6      bad
chromium@488746                    5149593 +- 50450.8      6      bad
chromium@488747                    5144212 +- 43323.7      6      bad
chromium@488748                    5166936 +- 48393.4      6      bad
chromium@488754                    5155953 +- 46204.7      6      bad
chromium@488766                    5172351 +- 62579.7      6      bad
chromium@488789                    5162849 +- 67349.4      6      bad
chromium@488836                    5158663 +- 31016.3      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

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8973085331180817792


For feedback, file a bug with component Speed>Bisection