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

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


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

chromium-rel-win10

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

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

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : media.tough_video_cases_tbmv2
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/video.html?src_crowd720_vp9.webm

Revision             Result                  N
chromium@488857      5564904 +- 943441       21      good
chromium@488861      5440073 +- 1188973      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.crowd720.vp9.webm 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/8973089044777720896


For feedback, file a bug with component Speed>Bisection

Looks recovered.