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

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


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

chromium-rel-win7-gpu-nvidia

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

=== 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:malloc:effective_size_avg/video.html?src_crowd.ogg_type_audio

Revision             Result                  N
chromium@488196      11600493 +- 226256      21      good
chromium@488285      11591923 +- 210312      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.crowd.ogg.type.audio 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/8973077128637614784


For feedback, file a bug with component Speed>Bisection

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