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

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


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

health-plan-webview-phone

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

=== 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-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:malloc:allocated_objects_size_avg/background_search/background_search_google
  Change       : 2.07% | 64312434.6667 -> 65642345.3333

Revision                                       Result                   N
android-chrome@bfbc254ab1                      64312435 +- 191448       6      good
android-chrome@bfbc254ab1,chromium@568611      64423139 +- 90093.4      6      good
android-chrome@bfbc254ab1,chromium@568613      64330991 +- 118777       6      good
android-chrome@bfbc254ab1,chromium@568614      66153867 +- 1045565      6      bad       <--
android-chrome@bfbc254ab1,chromium@568615      66459857 +- 1002416      6      bad
android-chrome@bfbc254ab1,chromium@568623      65909757 +- 1009314      6      bad
android-chrome@bfbc254ab1,chromium@568638      66681565 +- 1174666      6      bad
android-chrome@bfbc254ab1,chromium@568670      66368547 +- 1038381      6      bad
android-chrome@3447e60a36                      65838029 +- 983509       6      bad
android-chrome@2112fdecff                      65642345 +- 691693       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 --story-filter=background.search.google 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/8943022147479292944


For feedback, file a bug with component Speed>Bisection