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

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


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

linux-release

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : v8.infinite_scroll-ignition_tbmv2
  Metric       : v8-gc-incremental-step_max/v8-gc-incremental-step_max

Revision             Result                  N
chromium@453946      1.8013 +- 0.75868       21      good
chromium@454036      1.7915 +- 0.851265      21      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 v8.infinite_scroll-ignition_tbmv2

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

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


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

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

Looks like only two of the pages (twitter and tumblr) were affected, and that the range isn't clear. Kicked off two more bisects, one on each page, with a wider range.

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : v8.infinite_scroll-ignition_tbmv2
  Metric       : v8-gc-incremental-step_max/twitter

Revision             Result                  N
chromium@453946      2.35733 +- 3.09482      21      good
chromium@454121      2.28424 +- 3.04264      21      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=twitter v8.infinite_scroll-ignition_tbmv2

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

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


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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: linux_perf_bisect
  Benchmark    : v8.infinite_scroll-ignition_tbmv2
  Metric       : v8-gc-incremental-step_max/tumblr

Revision             Result                  N
chromium@453946      2.70643 +- 2.7586       21      good
chromium@454121      2.56776 +- 2.79298      21      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=tumblr v8.infinite_scroll-ignition_tbmv2

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

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


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

All alerts have been disassociated from teh bug? Closing.

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

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