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

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


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

android-one

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

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


===== TESTED REVISIONS =====
Revision                       Mean     Std Dev  N  Good?
chromium@418232                24143.6  2321.05  5  good
chromium@418240                21292.4  1231.6   5  good
chromium@418242                22043.8  2897.38  5  good
chromium@418242,v8@2ab3fcf42f  35375.8  3640.6   5  bad
chromium@418243                38245.8  1806.21  5  bad
chromium@418244                39059.8  4056.18  5  bad
chromium@418248                41041.6  3466.76  5  bad
chromium@418264                37677.2  2600.76  5  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 646830

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:new_space:allocated_objects_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:new_space:allocated_objects_size_avg
Relative Change: 56.05%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_one_perf_bisect/builds/1617
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9001540501641649072


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

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

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

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


===== TESTED REVISIONS =====
Revision                       Mean     Std Dev  N  Good?
chromium@418224                1192142  8182.54  5  good
chromium@418242                1188816  12517.2  5  good
chromium@418242,v8@28bd118148  1289123  7372.26  5  bad
chromium@418242,v8@2ab3fcf42f  1302040  5834.88  5  bad
chromium@418243                1287276  10716.8  5  bad
chromium@418244                1296647  11639.5  5  bad
chromium@418245                1296035  10423.0  5  bad
chromium@418247                1292883  7143.86  5  bad
chromium@418251                1300611  10427.4  5  bad
chromium@418259                1304960  6962.41  5  bad

Bisect job ran on: android_nexus6_perf_bisect
Bug ID: 646830

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:code_space:allocated_objects_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:code_space:allocated_objects_size_avg
Relative Change: 9.46%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus6_perf_bisect/builds/2562
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9001087071978217360


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

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

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

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

Please try rerunning the bisect.


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


Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:new_space:allocated_objects_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:new_space:allocated_objects_size_avg

Revision             Result                  N
chromium@418232      21567.2 +- 3286.83      9      good
chromium@418264      23537.6 +- 1251.57      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 --also-run-disabled-tests memory.top_10_mobile

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

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


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