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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg6ZfNoAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgmdz2uwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg6ef3ugoM


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

android-nexus5
android-nexus7v2

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

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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@417988  1153945  2097.17  8  good
chromium@418014  1156096  4194.33  8  good
chromium@418016  1163673  3950.01  5  bad
chromium@418018  1162035  3792.16  8  bad
chromium@418021  1162035  3792.16  8  bad
chromium@418027  1161856  3662.59  8  bad
chromium@418039  1162240  3959.08  8  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 646860

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests memory.top_10_mobile_stress
Test Metric: background-memory:chrome:all_processes:reported_by_os:system_memory:ashmem:proportional_resident_size_avg/after_http_search_yahoo_com_search__ylt_p_google
Relative Change: 0.55%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4124
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9001536420705108784


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

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

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

=== 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_nexus5_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  Metric       : background-memory:chrome:all_processes:reported_by_os:system_memory:ashmem:proportional_resident_size_avg/after_http_search_yahoo_com_search__ylt_p_google

Suspected Commit Range
  1 commits in range
  https://chromium.googlesource.com/chromium/src/+log/a74d3cbc572fa1c85cc2c0434a9f8e2f9cba0cd9..b63103ad596cb2deaf5151dd81de45de688dedeb


Revision             Result                  N
chromium@417988      1153945 +- 2097.17      8      good
chromium@418014      1156096 +- 4194.33      8      good
chromium@418016      1163673 +- 3950.01      5      bad
chromium@418018      1162035 +- 3792.16      8      bad
chromium@418021      1162035 +- 3792.16      8      bad
chromium@418027      1161856 +- 3662.59      8      bad
chromium@418039      1162240 +- 3959.08      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_stress

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

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


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