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

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


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

chromium-rel-win10
chromium-rel-win7-gpu-intel

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

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

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

Revision             Result                  N
chromium@488838      5531355 +- 1085379      21      good
chromium@488861      5606254 +- 840731       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/8973145010339858720


For feedback, file a bug with component Speed>Bisection

Bisect didn't find a culprit, and now the regression is stale.