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

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


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

chromium-rel-win10

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

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

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : media.desktop
  Metric       : memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/video.html?src_tulip2.vp9.webm

Revision             Result                  N
chromium@515101      3626283 +- 4530228      21      good
chromium@515129      3925867 +- 3773649      21      bad

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=video.html.src.tulip2.vp9.webm media.desktop

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

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


For feedback, file a bug with component Speed>Bisection

No regression found.