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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg9YWT_QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg9ajntgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg9dKkswoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgte7x9AgM


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

chromium-rel-win10
chromium-rel-win7-gpu-intel
chromium-rel-win8-dual

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

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


===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N   Good?
chromium@422857  14130580  575179   18  good
chromium@422878  14474711  717371   18  good
chromium@422884  14268127  636532   12  good
chromium@422886  15413623  716492   12  bad
chromium@422887  15186728  506337   8   bad
chromium@422889  15328139  508958   18  bad
chromium@422899  15415002  747352   18  bad

Bisect job ran on: winx64intel_perf_bisect
Bug ID: 653843

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests v8.browsing_desktop
Test Metric: memory:chrome:renderer_processes:reported_by_chrome:v8:heap:code_space:allocated_objects_size_max/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:code_space:allocated_objects_size_max
Relative Change: 10.78%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/winx64intel_perf_bisect/builds/1194
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8999463671789623472


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

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

=== 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: b873e02f086898e946c374f628fdc7b1cb47ce37
  bad_revision : 022a7317076c57094cd6137ded6e9be08b666f12

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


Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:code_space:allocated_objects_size_max/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:code_space:allocated_objects_size_max

Revision             Result                   N
chromium@422857      14774163 +- 2784383      14      good
chromium@422878      15116035 +- 2343784      14      good
chromium@422884      14482238 +- 2029586      9       good
chromium@422886      15625885 +- 1657170      9       bad
chromium@422887      15610724 +- 2739080      14      bad
chromium@422889      15715545 +- 2925436      21      bad
chromium@422899      15781418 +- 1622130      14      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests v8.browsing_desktop

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

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


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

This regression has been included in a stable release and that stable channel is now deprecated. I'm closing this so that we won't have unresponsive performance regressions in the future.