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

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


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

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

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

=== 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-phone-1024-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/browse_social/browse_social_pinterest_infinite_scroll
  Change       : 1096.34% | 668100.0 -> 7992772.0

Revision                                       Result                  N
android-chrome@132390eaab                      668100 +- 16826.0       6       good
android-chrome@009b09f963                      669807 +- 16190.9       9       good
android-chrome@dff611cf06                      2311165 +- 3229886      9       good
android-chrome@bfbc254ab1                      3293929 +- 3634520      14      good
android-chrome@bfbc254ab1,chromium@568611      3816022 +- 3753716      14      good
android-chrome@bfbc254ab1,chromium@568613      1901679 +- 2984014      6       good
android-chrome@bfbc254ab1,chromium@568614      7992772 +- 0.0          9       bad       <--
android-chrome@bfbc254ab1,chromium@568615      7992772 +- 0.0          14      bad
android-chrome@bfbc254ab1,chromium@568623      7992772 +- 0.0          9       bad
android-chrome@bfbc254ab1,chromium@568638      7992772 +- 0.0          9       bad
android-chrome@bfbc254ab1,chromium@568669      7992772 +- 0.0          9       bad
android-chrome@3447e60a36                      7992772 +- 0.0          9       bad
android-chrome@f8d0becf9b                      7992772 +- 0.0          6       bad
android-chrome@5698a49463                      7992772 +- 0.0          6       bad
android-chrome@b268028c43                      7992772 +- 0.0          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-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.social.pinterest.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/8942759390611617040


For feedback, file a bug with component Speed>Bisection