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

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


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

health-plan-clankium-phone
perf-go-phone-1024
perf-monochrome-n-phone

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

=== 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:effective_size_avg/browse_chrome/browse_chrome_newtab
  Change       : 35.20% | 865796.0 -> 1170560.0

Revision                                                     Result              N
android-chrome@74662f91c8                                    865796 +- 0.0       6      good
android-chrome@74662f91c8,chromium@575926                    865796 +- 0.0       6      good
android-chrome@74662f91c8,chromium@575929                    865796 +- 0.0       6      good
android-chrome@74662f91c8,chromium@575929,v8@e3a5b1e402      1170560 +- 0.0      6      bad
android-chrome@74662f91c8,chromium@575929,v8@16af1baac4      1170560 +- 0.0      6      bad
android-chrome@74662f91c8,chromium@575930                    1170560 +- 0.0      6      bad
android-chrome@74662f91c8,chromium@575931                    1170560 +- 0.0      6      bad
android-chrome@74662f91c8,chromium@575935                    1170560 +- 0.0      6      bad
android-chrome@1032e70048                                    1170560 +- 0.0      6      bad
android-chrome@4e67b217c5                                    1170560 +- 0.0      6      bad
android-chrome@bdf6ddc146                                    1170560 +- 0.0      6      bad
android-chrome@478583399d                                    1170560 +- 0.0      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.chrome.newtab 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/8940539902070898272


For feedback, file a bug with component Speed>Bisection