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

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


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

chromium-rel-win7-dual

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

=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: win_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

Revision             Result                     N
chromium@485433      566235676 +- 62001264      21      good

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/8974154888329117568


For feedback, file a bug with component Speed>Bisection