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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgxJH9rAkM


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

android-nexus6

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg
  Change       : 1.46% | 4805013.43333 -> 4875150.7

Suspected Commit Range
  6 commits in range
  https://chromium.googlesource.com/chromium/src/+log/16f4b5e65d6231e2cdb9ce4c5915cdebd056bef5..a19cc1934ae522d7b4a78fa466ca364ab10c83b8


Revision             Result                  N
chromium@452891      4805013 +- 76004.0      6        good
chromium@452931      4784411 +- 59944.7      6        good
chromium@452951      4823258 +- 90478.1      9        good
chromium@452953      4811432 +- 51916.1      6        good
chromium@452954      ---                     ---      build failure
chromium@452955      ---                     ---      build failure
chromium@452956      ---                     ---      build failure
chromium@452957      ---                     ---      build failure
chromium@452958      ---                     ---      build failure
chromium@452959      4875198 +- 24573.2      9        bad
chromium@452961      4892253 +- 56397.6      6        bad
chromium@452970      4875169 +- 42880.3      6        bad
chromium@453051      4875151 +- 39256.6      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-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests memory.top_10_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8986517855222766448

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6466593569112064


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

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