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

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


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

health-plan-clankium-phone
perf-go-phone-1024
perf-go-webview-phone

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: go-phone-1024-perf-bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/background/after_http_m_youtube_com_results_q_science
  Change       : 0.00% | 20207543.4286 -> 20207055.8095

Revision                       Result                  N
android-chrome@478583399d      20207543 +- 259517      21      good
android-chrome@5bcd964863      20207056 +- 123135      21      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=http.m.youtube.com.results.q.science memory.top_10_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8940541584133298832


For feedback, file a bug with component Speed>Bisection

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

=== 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: clankium-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/long_running_tools/long_running_tools_gmail-background
  Change       : 0.98% | 122820779.053 -> 124020197.83

Revision                                       Result                   N
android-chrome@74662f91c8                      122820779 +- 741547      14      good
android-chrome@74662f91c8,chromium@575935      123857015 +- 678761      9       bad
android-chrome@1032e70048                      124066175 +- 839900      14      bad
android-chrome@4e67b217c5                      123792314 +- 407955      9       bad
android-chrome@22c1f49355                      123771305 +- 569494      9       bad
android-chrome@934b6671a2                      124020198 +- 438203      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=long.running.tools.gmail.background 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/8940468685880589712


For feedback, file a bug with component Speed>Bisection