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

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


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

chromium-rel-win8-dual

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

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : v8.infinite_scroll_tbmv2
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/flickr


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

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


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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : mlippautz
  Commit : bf74d43de055393d97a3db4f01e4c832e35af10f
  Date   : Wed May 03 21:31:06 2017
  Subject: [heap] MinorMC: Evacuation for young generation

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : v8.infinite_scroll_tbmv2
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/flickr
  Change       : 3.36% | 24178688.0 -> 24991061.3333

Revision                           Result                  N
chromium@469246                    24178688 +- 490427      6      good
chromium@469253                    24309760 +- 980853      6      good
chromium@469257                    24397141 +- 478607      6      good
chromium@469258                    24266069 +- 239304      6      good
chromium@469258,v8@bf74d43de0      25034752 +- 888974      6      bad       <--
chromium@469258,v8@ff8039d73a      24903680 +- 370728      6      bad
chromium@469259                    25340587 +- 800863      6      bad
chromium@469260                    25122133 +- 779116      6      bad
chromium@469274                    25034752 +- 807982      6      bad
chromium@469301                    24991061 +- 800863      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/8980175235221499744

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


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