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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgzNCStgsM


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

chromium-rel-mac12-mini-8gb

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

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

Bisect Details
  Configuration: mac_10_12_mini_8gb_perf_bisect
  Benchmark    : media.tough_video_cases
  Metric       : vm_resident_set_size_delta_size/video.html?src_crowd.wav_type_audio

Revision             Result                  N
chromium@456813      5963.43 +- 2242.74      21      good
chromium@456969      6106.1 +- 1716.07       21      bad

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.crowd.wav.type.audio media.tough_video_cases

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8984288824453656368

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5870471989428224


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

Could this be: https://chromium.googlesource.com/chromium/src/+/0d7277979d62a3b3efc707fb52d3b45b727a04a4

https://chromium.googlesource.com/chromium/src/+/0d7277979d62a3b3efc707fb52d3b45b727a04a4 added a new benchmark media.tough_video_cases_tbmv2. It made no changes to media.tough_video_cases at all (that will happen in the future), so it's unlikely to cause regressions in media.tough_video_cases.

Numbers came back to normal.