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

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


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

chromium-rel-win7-gpu-nvidia

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

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

Bisect Details
  Configuration: winx64nvidia_perf_bisect
  Benchmark    : media.tough_video_cases_tbmv2
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/video.html?src_crowd1080.mp4

Revision             Result                  N
chromium@488862      5481423 +- 1166748      21      good
chromium@488875      5556322 +- 1023305      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.crowd1080.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/8973145036084238432


For feedback, file a bug with component Speed>Bisection

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