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

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


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

health-plan-webview-phone
perf-go-phone-512

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

=== 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-512-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       : 5.59% | 22627433.3333 -> 23891802.0

Revision                                       Result                  N
android-chrome@5cb3f5852f                      22627433 +- 489716      6       good
android-chrome@7f8fc8ca89                      22755589 +- 225912      6       good
android-chrome@45a49de40d                      22587741 +- 493220      6       good
android-chrome@5060b21f7f                      22885100 +- 513253      6       good
android-chrome@96555ff9c3                      22827903 +- 344310      9       good
android-chrome@96555ff9c3,chromium@573466      22773356 +- 213391      6       good
android-chrome@96555ff9c3,chromium@573545      22606150 +- 453007      14      good
android-chrome@96555ff9c3,chromium@573565      22477283 +- 306313      6       good
android-chrome@96555ff9c3,chromium@573568      22559630 +- 188445      9       good
android-chrome@96555ff9c3,chromium@573569      22753499 +- 374002      14      good
android-chrome@96555ff9c3,chromium@573570      23335628 +- 388409      9       bad       <--
android-chrome@96555ff9c3,chromium@573575      23465453 +- 643339      6       bad
android-chrome@96555ff9c3,chromium@573584      23352224 +- 508758      14      bad
android-chrome@0c23a72c68                      23346267 +- 335318      9       bad
android-chrome@7b94b395a3                      23468630 +- 472465      13      bad
android-chrome@b291a7ceb9                      23567630 +- 410047      9       bad
android-chrome@801e0585fe                      23891802 +- 178402      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.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/8940665697465977184


For feedback, file a bug with component Speed>Bisection