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

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


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

health-plan-clankium-low-end-phone

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

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

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: d479013f0ea07513550c7ec7f8c81e08ad2a19d4
  bad_revision : 42fff895da60983dfb314079bc0493c59051c41b

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


Bisect Details
  Configuration: clankium-low-end-phone-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       : 3.29% | 19664126.5714 -> 20310738.6667

Revision                                       Result                  N
android-chrome@96555ff9c3                      19664127 +- 233962      14      good
android-chrome@96555ff9c3,chromium@573466      19719303 +- 281152      14      good
android-chrome@96555ff9c3,chromium@573545      19695725 +- 226754      14      good
android-chrome@96555ff9c3,chromium@573565      19670175 +- 359036      14      good
android-chrome@96555ff9c3,chromium@573575      20386910 +- 484791      14      bad
android-chrome@96555ff9c3,chromium@573584      20278852 +- 464505      9       bad
android-chrome@0c23a72c68                      20178897 +- 508084      14      bad
android-chrome@7b94b395a3                      20448307 +- 635985      6       bad
android-chrome@cd63705090                      20377241 +- 659081      6       bad
android-chrome@cb4b582a48                      20310739 +- 603476      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/8941217302818504608


For feedback, file a bug with component Speed>Bisection

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: clankium-low-end-phone-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


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/8940857588545125024


For feedback, file a bug with component Speed>Bisection

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

=== 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:effective_size_avg/browse_social/browse_social_facebook_infinite_scroll
  Change       : 2.71% | 19774616.0 -> 20309644.8889

Revision                                       Result                  N
android-chrome@3d062ddc07                      19774616 +- 435166      14      good
android-chrome@576bca3272                      19729680 +- 405466      9       good
android-chrome@96555ff9c3                      19700143 +- 422248      14      good
android-chrome@96555ff9c3,chromium@573466      19733187 +- 305924      14      good
android-chrome@96555ff9c3,chromium@573545      19580345 +- 197149      6       good
android-chrome@96555ff9c3,chromium@573565      19637511 +- 376260      14      good
android-chrome@96555ff9c3,chromium@573568      19736515 +- 456240      14      good
android-chrome@96555ff9c3,chromium@573569      19477672 +- 349081      6       good
android-chrome@96555ff9c3,chromium@573570      20330579 +- 392374      14      bad       <--
android-chrome@96555ff9c3,chromium@573575      20374143 +- 427144      14      bad
android-chrome@96555ff9c3,chromium@573584      20227045 +- 294613      9       bad
android-chrome@0c23a72c68                      20279525 +- 445210      14      bad
android-chrome@7b94b395a3                      20146094 +- 265611      9       bad
android-chrome@cd63705090                      20329844 +- 338320      9       bad
android-chrome@6a69fc540e                      20472571 +- 410071      6       bad
android-chrome@01d7a253b4                      20309645 +- 332751      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/8940855413036054384


For feedback, file a bug with component Speed>Bisection