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

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


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

perf-go-phone-1024

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

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

 Issue 863325  has been merged into this issue.

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: go-phone-1024-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/browse_social/browse_social_facebook_infinite_scroll
  Change       : 2.43% | 22848761.7143 -> 23403726.2222

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/bda2c4df785721b35cdf789f89d6a3291a97a889..d7ae73502ade3255987a4b5c72c5294c2c82896a


Revision                                       Result                  N
android-chrome@96555ff9c3                      22848762 +- 418001      14       good
android-chrome@96555ff9c3,chromium@573466      22727767 +- 142117      6        good
android-chrome@96555ff9c3,chromium@573545      22698221 +- 271745      6        good
android-chrome@96555ff9c3,chromium@573565      22734355 +- 392968      14       good
android-chrome@96555ff9c3,chromium@573568      22752832 +- 286649      14       good
android-chrome@96555ff9c3,chromium@573569      ---                     ---      build failure
android-chrome@96555ff9c3,chromium@573570      23336337 +- 549238      14       bad
android-chrome@96555ff9c3,chromium@573575      23611007 +- 229027      9        bad
android-chrome@96555ff9c3,chromium@573584      23442544 +- 480538      9        bad
android-chrome@0c23a72c68                      23577517 +- 542583      6        bad
android-chrome@7b94b395a3                      23510063 +- 497675      9        bad
android-chrome@cd63705090                      23449733 +- 258257      6        bad
android-chrome@cb4b582a48                      23403726 +- 430735      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.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/8941131286908394224


For feedback, file a bug with component Speed>Bisection

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Michael Thiessen
  Commit : d7ae73502ade3255987a4b5c72c5294c2c82896a
  Date   : Tue Jul 10 00:57:13 2018
  Subject: ALooper implementation for MessagePumpForUI::Schedule(Delayed)Work

Bisect Details
  Configuration: go-phone-1024-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/browse_social/browse_social_facebook_infinite_scroll
  Change       : 1.84% | 22886883.1429 -> 23309045.1429

Revision                                       Result                  N
android-chrome@96555ff9c3                      22886883 +- 338724      14      good
android-chrome@96555ff9c3,chromium@573466      22795157 +- 456225      9       good
android-chrome@96555ff9c3,chromium@573545      22878231 +- 357449      9       good
android-chrome@96555ff9c3,chromium@573565      22801753 +- 246065      9       good
android-chrome@96555ff9c3,chromium@573568      22822946 +- 383555      14      good
android-chrome@96555ff9c3,chromium@573569      22958589 +- 267863      14      good
android-chrome@96555ff9c3,chromium@573570      23538871 +- 496945      9       bad       <--
android-chrome@96555ff9c3,chromium@573575      23528474 +- 226376      6       bad
android-chrome@96555ff9c3,chromium@573584      23649749 +- 583066      9       bad
android-chrome@0c23a72c68                      23418209 +- 294251      9       bad
android-chrome@7b94b395a3                      23519463 +- 494987      9       bad
android-chrome@cd63705090                      23831962 +- 479125      6       bad
android-chrome@cb4b582a48                      23309045 +- 391242      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.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/8941131250608083056


For feedback, file a bug with component Speed>Bisection