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

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


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

perf-go-phone-512

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

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

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


Bisect Details
  Configuration: go-phone-512-perf-bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:private_dirty_size_avg/foreground/http_m_intl_taobao_com_group_purchase_html


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


For feedback, file a bug with component Speed>Bisection

Downgrading P2s that haven't been modified in more than 6 months, which have no component or owner.