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

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


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

chromium-rel-win7-dual

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

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

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : media.tough_video_cases
  Metric       : vm_working_set_delta_size/video.html?src_garden2_10s.webm_canvas_true

Revision             Result                 N
chromium@456973      388357 +- 3635.19      21      good
chromium@457046      388700 +- 2955.76      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.garden2.10s.webm.canvas.true media.tough_video_cases

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

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


| 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!

Will do another with wider range. 

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

=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : sugoi
  Commit : 842efc6922b0cd66febd6f36f04318ebf396c184
  Date   : Tue Mar 14 18:10:39 2017
  Subject: Moving SwiftShader from component to bundled library

Bisect Details
  Configuration: win_perf_bisect
  Benchmark    : media.tough_video_cases
  Metric       : vm_working_set_delta_size/video.html?src_garden2_10s.webm_canvas_true
  Change       : 1.16% | 377144.444444 -> 381508.444444

Revision             Result                 N
chromium@456700      377144 +- 2055.86      9       good
chromium@456763      377487 +- 3466.22      9       good
chromium@456764      380400 +- 2716.79      6       bad       <--
chromium@456765      380253 +- 2621.71      6       bad
chromium@456767      383247 +- 17718.9      6       bad
chromium@456771      380182 +- 2085.2       6       bad
chromium@456779      379928 +- 2931.96      9       bad
chromium@456794      379275 +- 5834.69      14      bad
chromium@456825      379837 +- 4248.24      9       bad
chromium@456950      380900 +- 2191.15      6       bad
chromium@457200      381508 +- 18180.2      9       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.garden2.10s.webm.canvas.true media.tough_video_cases

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

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


| 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!