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

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


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

android-nexus9

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

===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean    Std Dev  N  Good?
chromium@416076  199525  733.581  8  good
chromium@416091  198747  1046.97  8  good
chromium@416098  199182  910.638  8  good
chromium@416101  198677  944.342  8  good
chromium@416103  199567  199.946  5  good
chromium@416104  201283  1317.86  8  bad

Bisect job ran on: android_nexus9_perf_bisect
Bug ID: 644259

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests memory.top_10_mobile
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:v8:heap:map_space:allocated_objects_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:map_space:allocated_objects_size_avg
Relative Change: 0.79%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/2092
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9002261248268876336


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5273589253668864

| 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 Tests>AutoBisect.  Thank you!

Recovered already.

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

=== 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_nexus9_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:map_space:allocated_objects_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:map_space:allocated_objects_size_avg

Suspected Commit Range
  1 commits in range
  https://chromium.googlesource.com/chromium/src/+log/fadb58864d3a99cd09b89d31994d4286f4cb60d2..77d1f985eaad21ef85fbee669b7ecf61c8cf6faf


Revision             Result                 N
chromium@416076      199525 +- 733.581      8      good
chromium@416091      198747 +- 1046.97      8      good
chromium@416098      199182 +- 910.638      8      good
chromium@416101      198677 +- 944.342      8      good
chromium@416103      199567 +- 199.946      5      good
chromium@416104      201283 +- 1317.86      8      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 --also-run-disabled-tests memory.top_10_mobile

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

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


| 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!