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

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


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

chromium-rel-win8-dual

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

=== 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: win_8_perf_bisect
  Benchmark    : v8.infinite_scroll_tbmv2
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/flickr

Revision                           Result                  N
chromium@477434                    24305079 +- 686454      7      good
chromium@477442                    24167765 +- 605396      6      good
chromium@477446                    23949312 +- 262144      4      good
chromium@477448                    24255147 +- 605396      6      good
chromium@477448,v8@8a15026270      24080384 +- 370728      6      good
chromium@477449                    25225899 +- 685261      6      bad
chromium@477450                    24890937 +- 941126      9      bad
chromium@477465                    25051136 +- 586172      4      bad
chromium@477496                    25225899 +- 685261      6      bad
chromium@477557                    25182208 +- 524288      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=flickr v8.infinite_scroll_tbmv2

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

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


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

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

=== 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: win_8_perf_bisect
  Benchmark    : v8.infinite_scroll_tbmv2
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/flickr

Revision                           Result                  N
chromium@477434                    24211456 +- 614782      6      good
chromium@477442                    24237670 +- 597780      5      good
chromium@477446                    24145920 +- 434717      4      good
chromium@477448                    24124075 +- 239304      6      good
chromium@477448,v8@8a15026270      24155282 +- 610777      7      good
chromium@477449                    25138517 +- 685261      6      bad
chromium@477450                    25107310 +- 610777      7      bad
chromium@477465                    25225899 +- 576319      6      bad
chromium@477496                    24788992 +- 321060      6      bad
chromium@477557                    25182208 +- 642119      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=flickr v8.infinite_scroll_tbmv2

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

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


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

Most of these bugs re v8.infinite_scroll_tbmv2 should be handled through  Issue 724262  .

The graph recovered.