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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=5c6c8b7b55718da9d5b47ff2f1da07c2e1942332a04235e78e3532582bbf1973


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

chromium-rel-mac-retina
chromium-rel-mac11-air
chromium-rel-win7-dual

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

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

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


Bisect Details
  Configuration: mac_air_perf_bisect
  Benchmark    : v8.browsing_desktop
  Metric       : v8-gc-latency-mark-compactor_max/browse_social/browse_social_facebook_infinite_scroll


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=browse.social.facebook.infinite.scroll v8.browsing_desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8970556912307020224


For feedback, file a bug with component Speed>Bisection

Simon, can you have a look?

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

Looks like one of the steps timed out, there's a bug open for that: crbug.com/664765

I'll try rekicking this.

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

Suspected Commit
  Author : Adam Rice
  Commit : f8a808d3178bd1b03fa002db5f6c0fa86881daa7
  Date   : Tue Aug 15 22:00:50 2017
  Subject: Streams: Throw for undefined values in pipeThrough

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/load_games/load_games_lazors
  Change       : 0.88% | 1904204.0 -> 1920944.0

Revision             Result              N
chromium@494517      1904204 +- 0.0      6      good
chromium@494549      1904204 +- 0.0      6      good
chromium@494565      1904204 +- 0.0      6      good
chromium@494566      1920944 +- 0.0      6      bad       <--
chromium@494567      1920944 +- 0.0      6      bad
chromium@494569      1920944 +- 0.0      6      bad
chromium@494573      1920944 +- 0.0      6      bad
chromium@494580      1920944 +- 0.0      6      bad
chromium@494643      1920944 +- 0.0      6      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

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=load.games.lazors system_health.memory_desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8970544861633204304


For feedback, file a bug with component Speed>Bisection