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

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


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

chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual
chromium-rel-win8-dual

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : media.tough_video_cases_tbmv2
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/video.html?src_crowd2160.mp4
  Change       : 4.01% | 423294448.333 -> 440289044.778

Suspected Commit Range
  4 commits in range
  https://chromium.googlesource.com/chromium/src/+log/96cbab92e2053621198dcef499ae6cca6a4b72de..7cd2f6bd73c6a9c6200704e995b18ebb3168ead6


Revision             Result                     N
chromium@495787      423294448 +- 18167240      9        good
chromium@495798      426199341 +- 31037648      14       good
chromium@495799      ---                        ---      build failure
chromium@495800      ---                        ---      build failure
chromium@495801      ---                        ---      build failure
chromium@495802      434990283 +- 32074063      21       bad
chromium@495803      434949731 +- 23174326      14       bad
chromium@495808      440289045 +- 23364719      9        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=video.html.src.crowd2160.mp4 media.tough_video_cases_tbmv2

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

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


For feedback, file a bug with component Speed>Bisection

assigning to thakis@ since the commit range seems pretty window-specific.  not sure if this is WAI with the clang change or not.