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

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


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

android-nexus7v2

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

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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@419253  65690.0  436.992  5  good
chromium@419280  65632.0  116.0    4  good
chromium@419284  75845.0  517.534  5  bad
chromium@419287  75597.4  553.203  5  bad
chromium@419293  75675.0  311.435  5  bad
chromium@419306  76033.3  286.676  6  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 648166

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

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3318
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9001105329946517456


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

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

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


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@419253  65566.4  276.378  5  good
chromium@419280  65445.3  302.821  6  good
chromium@419284  76092.6  276.378  5  bad
chromium@419287  76092.4  517.415  5  bad
chromium@419293  75659.5  357.38   4  bad
chromium@419306  75721.4  339.04   5  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 648166

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests system_health.memory_mobile
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:v8:heap:large_object_space:effective_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:large_object_space:effective_size_avg
Relative Change: 15.49%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3387
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999088205940890272


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

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

Closing this since it is only large object space regression, not the total heap.