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

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


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

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

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

Please try rerunning the bisect.


If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: go-phone-1024-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_avg/browse_social/browse_social_facebook_infinite_scroll
  Change       : 2.42% | 20933808.5714 -> 21440288.0

Revision                                       Result                  N
android-chrome@96555ff9c3                      20933809 +- 229410      14      good
android-chrome@96555ff9c3,chromium@573466      20957386 +- 226630      6       good
android-chrome@96555ff9c3,chromium@573545      20917349 +- 256951      9       good
android-chrome@0c23a72c68                      21492549 +- 356791      9       bad
android-chrome@7b94b395a3                      21368496 +- 385189      9       bad
android-chrome@cd63705090                      21632845 +- 165809      6       bad
android-chrome@cb4b582a48                      21440288 +- 421210      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/8941217315000503952


For feedback, file a bug with component Speed>Bisection

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

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

=== 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: clankium-low-end-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size_avg/browse_social/browse_social_facebook_infinite_scroll
  Change       : 2.68% | 17848736.8889 -> 18327842.0

Revision                                       Result                  N
android-chrome@96555ff9c3                      17848737 +- 241173      9       good
android-chrome@96555ff9c3,chromium@573466      17960393 +- 178236      9       good
android-chrome@96555ff9c3,chromium@573545      17968598 +- 212061      9       good
android-chrome@96555ff9c3,chromium@573565      17932024 +- 321068      14      good
android-chrome@96555ff9c3,chromium@573568      18004379 +- 280495      9       good
android-chrome@96555ff9c3,chromium@573569      17886754 +- 434153      9       good
android-chrome@96555ff9c3,chromium@573570      18499343 +- 345107      9       bad       <--
android-chrome@96555ff9c3,chromium@573575      18414172 +- 387943      9       bad
android-chrome@96555ff9c3,chromium@573584      18375816 +- 333248      14      bad
android-chrome@0c23a72c68                      18410497 +- 301427      9       bad
android-chrome@7b94b395a3                      18468788 +- 240790      6       bad
android-chrome@cd63705090                      18587880 +- 196128      6       bad
android-chrome@cb4b582a48                      18327842 +- 241532      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/8940855854027477920


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:allocated_objects_size_avg/browse_social/browse_social_facebook_infinite_scroll
  Change       : 2.50% | 21010597.7143 -> 21520820.8889

Revision                                       Result                  N
android-chrome@96555ff9c3                      21010598 +- 289465      14      good
android-chrome@96555ff9c3,chromium@573486      21005109 +- 388925      21      good
android-chrome@96555ff9c3,chromium@573545      20820965 +- 191530      9       good
android-chrome@96555ff9c3,chromium@573565      20959490 +- 337785      14      good
android-chrome@96555ff9c3,chromium@573568      20884009 +- 274719      14      good
android-chrome@96555ff9c3,chromium@573569      21113157 +- 366721      21      good
android-chrome@96555ff9c3,chromium@573570      21462157 +- 315568      14      bad       <--
android-chrome@96555ff9c3,chromium@573575      21479496 +- 178689      6       bad
android-chrome@96555ff9c3,chromium@573584      21455788 +- 283586      9       bad
android-chrome@0c23a72c68                      21356069 +- 236623      14      bad
android-chrome@7b94b395a3                      21373868 +- 393079      21      bad
android-chrome@cd63705090                      21421715 +- 219094      14      bad
android-chrome@cb4b582a48                      21520821 +- 353101      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/8940855847702334496


For feedback, file a bug with component Speed>Bisection