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

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


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

perf-go-phone-512

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

=== 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-512-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_cnn
  Change       : 9.99% | 7599053.2381 -> 8358178.57143

Revision                                       Result                  N
android-chrome@bfbc254ab1                      7599053 +- 867708       21      good
android-chrome@bfbc254ab1,chromium@568611      7296144 +- 435027       14      good
android-chrome@bfbc254ab1,chromium@568613      7582279 +- 718679       21      good
android-chrome@bfbc254ab1,chromium@568614      8532356 +- 1070882      21      bad       <--
android-chrome@bfbc254ab1,chromium@568615      8364030 +- 836214       14      bad
android-chrome@bfbc254ab1,chromium@568623      8435482 +- 773700       9       bad
android-chrome@bfbc254ab1,chromium@568639      8596137 +- 137705       6       bad
android-chrome@bfbc254ab1,chromium@568670      8627637 +- 710542       14      bad
android-chrome@3447e60a36                      8538110 +- 858035       14      bad
android-chrome@2112fdecff                      8358179 +- 1111171      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-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.cnn 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/8942756401698882992


For feedback, file a bug with component Speed>Bisection