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

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


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

health-plan-webview-low-end-phone
perf-go-phone-1024
perf-go-phone-512

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

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

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

Hi sigurds@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 : Sigurd Schneider
  Commit : f5a8352b0fbba0d88104de7949a0d0c238765cf8
  Date   : Tue Jun 19 11:39:09 2018
  Subject: [embedded-builtins] Enable on all arches except x86 for benchmarks

Bisect Details
  Configuration: go-phone-1024-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/browse_news/browse_news_qq
  Change       : 27.86% | 9291724.57143 -> 11880104.0

Revision                                                     Result                   N
android-chrome@132390eaab                                    9291725 +- 1623468       14      good
android-chrome@009b09f963                                    9653635 +- 1640070       14      good
android-chrome@dff611cf06                                    8749850 +- 1237287       9       good
android-chrome@bfbc254ab1                                    8289277 +- 205857        6       good
android-chrome@bfbc254ab1,chromium@568638                    8658828 +- 1157013       9       good
android-chrome@bfbc254ab1,chromium@568654                    8989238 +- 1554158       9       good
android-chrome@bfbc254ab1,chromium@568654,v8@38bec2eadc      8567805 +- 1279007       9       good
android-chrome@bfbc254ab1,chromium@568654,v8@f5a8352b0f      11277407 +- 1320738      14      bad       <--
android-chrome@bfbc254ab1,chromium@568655                    11766326 +- 268161       9       bad
android-chrome@bfbc254ab1,chromium@568656                    11731965 +- 359268       6       bad
android-chrome@bfbc254ab1,chromium@568658                    11833000 +- 350037       6       bad
android-chrome@bfbc254ab1,chromium@568661                    11824125 +- 376838       9       bad
android-chrome@bfbc254ab1,chromium@568669                    11884200 +- 389219       6       bad
android-chrome@3447e60a36                                    11485133 +- 1392368      14      bad
android-chrome@f8d0becf9b                                    11611231 +- 971162       14      bad
android-chrome@5698a49463                                    11972492 +- 426875       9       bad
android-chrome@b268028c43                                    11880104 +- 395237       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-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.qq system_health.memory_mobile

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

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


For feedback, file a bug with component Speed>Bisection

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

Hi chaopeng@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 : chaopeng
  Commit : 4a2ebc8dad89ca0042d0babd619f4ea35e3ac072
  Date   : Tue Jun 19 22:09:03 2018
  Subject: Set TouchStartExpectedSoon only after we seen a blocking event

Bisect Details
  Configuration: webview-low-end-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:malloc:effective_size_avg/browse_news/browse_news_washingtonpost
  Change       : 0.69% | 28871957.9524 -> 29071479.4286

Revision                                       Result                   N
android-chrome@dff611cf06                      28871958 +- 171150       21      good
android-chrome@bfbc254ab1                      28905085 +- 107192       6       good
android-chrome@bfbc254ab1,chromium@568611      28845768 +- 187219       6       good
android-chrome@bfbc254ab1,chromium@568613      28865103 +- 66950.6      6       good
android-chrome@bfbc254ab1,chromium@568614      29136601 +- 28966.1      6       bad       <--
android-chrome@bfbc254ab1,chromium@568615      29225050 +- 128356       6       bad
android-chrome@bfbc254ab1,chromium@568623      29131705 +- 10295.8      6       bad
android-chrome@bfbc254ab1,chromium@568638      29135436 +- 16611.1      6       bad
android-chrome@bfbc254ab1,chromium@568669      29145830 +- 103224       6       bad
android-chrome@3447e60a36                      29071479 +- 208289       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-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.washingtonpost system_health.memory_mobile

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

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


For feedback, file a bug with component Speed>Bisection