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

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


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

perf-go-phone-1024

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

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

Error: TIMEOUT

The bisect was able to narrow the range, you can try running with:
  good_revision: 47afec87e14b5d33321a9969298c41548a6f8459
  bad_revision : 0ffeb3f08464644582f40e9e7c41ffdfab00a836

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


Bisect Details
  Configuration: go-phone-1024-perf-bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/foreground/http_m_intl_taobao_com_group_purchase_html
  Change       : 3.15% | 6887762.66667 -> 7104850.66667

Revision                                       Result                  N
android-chrome@b50c37440c                      6887763 +- 4027.15      6        good
android-chrome@b50c37440c,chromium@560639      6905805 +- 72540.7      14       good
android-chrome@b50c37440c,chromium@560641      ---                     ---      build failure
android-chrome@b50c37440c,chromium@560642      ---                     ---      build failure
android-chrome@b50c37440c,chromium@560643      ---                     ---      build failure
android-chrome@b50c37440c,chromium@560644      ---                     ---      build failure
android-chrome@b50c37440c,chromium@560645      ---                     ---      build failure
android-chrome@b50c37440c,chromium@560646      ---                     ---      build failure
android-chrome@b50c37440c,chromium@560648      6927747 +- 98244.4      14       bad
android-chrome@b50c37440c,chromium@560656      7150589 +- 5596.2       6        bad
android-chrome@b50c37440c,chromium@560690      7154003 +- 4788.41      6        bad
android-chrome@3e4ba1f0ce                      7152637 +- 4788.41      6        bad
android-chrome@5c07f907f2                      7104851 +- 100812       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=http.m.intl.taobao.com.group.purchase.html 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/8945072505443603792


For feedback, file a bug with component Speed>Bisection

bisect didn't actually repro this.