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

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


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

android-one

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

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


===== TESTED REVISIONS =====
Revision         Mean    Std Dev  N   Good?
chromium@418568  730629  5901.88  12  good
chromium@418619  738675  6274.56  12  bad
chromium@418669  742955  11735.0  12  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 647654

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: 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: 2.05%
Score: 0

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


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

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

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


===== TESTED REVISIONS =====
Revision         Mean    Std Dev  N  Good?
chromium@418573  654654  513.124  5  good
chromium@418621  666128  838.334  5  bad
chromium@418669  666173  1589.13  5  bad

Bisect job ran on: android_one_perf_bisect
Bug ID: 647654

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: 1.76%
Score: 0

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


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

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

It did not affect the total heap size, only code space.

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

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

Error: INFRA_FAILURE

The bisect was able to narrow the range, you can try running with:
  good_revision: f19502008401dc093629f3ca082f82edbc47e475
  bad_revision : 628a0b386bc8728a79e58934dbb14503e8cb0611

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


Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : memory.top_10_mobile_stress
  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

Revision             Result                 N
chromium@418568      696368 +- 5864.59      6      good
chromium@418619      706444 +- 12825.5      7      bad
chromium@418669      707258 +- 7072.51      5      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/8982651993594876208

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


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