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

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


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

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

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

=== 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: e4dc0ab81f77ab561d1ca7fa305510fe8613a8df
  bad_revision : 50257b9eafc8ec098a9693d4740fd761ace59c35

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:allocated_objects_size_avg/browse_social/browse_social_tumblr_infinite_scroll
  Change       : 7.46% | 40133127.2 -> 43126412.6667

Revision                                       Result                   N
android-chrome@9c123ef27e                      40133127 +- 502442       5      good
android-chrome@fce660687f                      40511352 +- 731816       6      good
android-chrome@fce660687f,chromium@560759      40719930 +- 1104821      5      good
android-chrome@fce660687f,chromium@560761      42955299 +- 585415       9      bad
android-chrome@fce660687f,chromium@560764      43400157 +- 445467       6      bad
android-chrome@fce660687f,chromium@560770      42852554 +- 894346       6      bad
android-chrome@fce660687f,chromium@560782      43002467 +- 442735       6      bad
android-chrome@fce660687f,chromium@560807      43360071 +- 715874       6      bad
android-chrome@fce660687f,chromium@560856      44056754 +- 407351       6      bad
android-chrome@a3dc2608ce                      43126413 +- 669858       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.tumblr.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/8945556605519203776


For feedback, file a bug with component Speed>Bisection