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

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


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

chromium-rel-win10

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

=== Auto-CCing suspected CL author ricea@chromium.org ===

Hi ricea@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== 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: winx64_10_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       : 1.10% | 3023264.0 -> 3056536.0

Revision             Result              N
chromium@494404      3023264 +- 0.0      6      good
chromium@494488      3023264 +- 0.0      6      good
chromium@494530      3023264 +- 0.0      6      good
chromium@494551      3023264 +- 0.0      6      good
chromium@494562      3023264 +- 0.0      6      good
chromium@494565      3023264 +- 0.0      6      good
chromium@494566      3056536 +- 0.0      6      bad       <--
chromium@494567      3056536 +- 0.0      6      bad
chromium@494572      3056536 +- 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_x64 --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/8971023470378582736


For feedback, file a bug with component Speed>Bisection

Same sort of thing as  issue 752172  and  issue 748279 . Minor change to Streams API implementation changes the layout of the V8 heap, resulting in apparent regression in memory usage.

 Issue 757793  has been merged into this issue.