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

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


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

perf-go-webview-phone

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

=== 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: go-webview-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:v8:allocated_objects_size_avg/browse_social/browse_social_facebook_infinite_scroll
  Change       : 42.52% | 15604398.0 -> 22240104.0

Revision                                       Result                   N
android-chrome@d79bf90511                      15604398 +- 134958       6      good
android-chrome@e90c9c80c5                      15934231 +- 812866       6      good
android-chrome@a5a5234c1c                      16179656 +- 1013367      6      good
android-chrome@6d7cb80987                      15407291 +- 249065       6      good
android-chrome@bfbc254ab1                      15927388 +- 977740       6      good
android-chrome@bfbc254ab1,chromium@568611      16031438 +- 671420       6      good
android-chrome@bfbc254ab1,chromium@568613      15721277 +- 581884       6      good
android-chrome@bfbc254ab1,chromium@568614      22405407 +- 195554       6      bad       <--
android-chrome@bfbc254ab1,chromium@568615      22460369 +- 543394       6      bad
android-chrome@bfbc254ab1,chromium@568623      22421325 +- 318633       6      bad
android-chrome@bfbc254ab1,chromium@568638      22220850 +- 241349       6      bad
android-chrome@bfbc254ab1,chromium@568669      21758701 +- 445336       6      bad
android-chrome@3447e60a36                      21305311 +- 437683       6      bad
android-chrome@2112fdecff                      21781805 +- 400471       5      bad
android-chrome@e08b47976c                      21747119 +- 664844       6      bad
android-chrome@08bcce2f90                      21498456 +- 200791       6      bad
android-chrome@12fcaddca5                      21878859 +- 469144       6      bad
android-chrome@8062d9e01c                      22240104 +- 355715       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=browse.social.facebook.infinite.scroll 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/8942389229593673152


For feedback, file a bug with component Speed>Bisection