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

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


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

android-one
chromium-rel-mac-retina
chromium-rel-mac11
chromium-rel-mac11-air
chromium-rel-mac11-pro
win-high-dpi

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

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

Bisect Details
  Configuration: winx64_high_dpi_perf_bisect
  Benchmark    : media.tough_video_cases_tbmv2
  Metric       : memory:chrome:all_processes:reported_by_chrome:gpu:effective_size_avg/video.html?src_crowd2160.mp4

Revision             Result                  N
chromium@497362      18049905 +- 210183      21      good
chromium@497405      18037812 +- 225129      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.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/8969999862185385728


For feedback, file a bug with component Speed>Bisection

Bisect couldn't reproduce and now they seem fixed; though the gpu memory one is binary, but likely unrelated to media.