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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7MmRugoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnImPjwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7LLEqAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7PDXpwsM


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

chromium-rel-mac11-air
chromium-rel-win10

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

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

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

Bisect Details
  Configuration: mac_air_perf_bisect
  Benchmark    : media.tough_video_cases
  Metric       : vm_resident_set_size_delta_size/video.html?src_crowd1080.webm

Revision             Result                  N
chromium@459664      85983.8 +- 22124.2      21      good
chromium@459675      85936.8 +- 22051.3      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.crowd1080.webm media.tough_video_cases

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

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


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

Hmm. Alert graphs showed a clear uptick. I'm unsure why the bisect failed on the outer range. Any ideas, crouleau@?

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

I'm trying a wider bisect range on one of the clearer alert upticks, just in case.

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

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

Bisect Details
  Configuration: mac_air_perf_bisect
  Benchmark    : media.tough_video_cases
  Metric       : vm_resident_set_size_delta_size/video.html?src_crowd1080.webm

Revision             Result                  N
chromium@459664      86116.0 +- 22078.7      21      good
chromium@459675      85930.3 +- 22529.6      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.crowd1080.webm media.tough_video_cases

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

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


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

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

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : media.tough_video_cases
  Metric       : vm_working_set_delta_size/crowd.wav_total

Revision             Result                  N
chromium@459662      33177.9 +- 4887.61      21      good
chromium@459674      32595.8 +- 6311.3       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 media.tough_video_cases

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

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


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

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

Suspected Commit
  Author : sugoi
  Commit : 7ae2ba1892a8b4dee8d7c231ac0e0fbe66588912
  Date   : Sat Mar 25 13:59:47 2017
  Subject: Solving some telemetry tests' slowness

Bisect Details
  Configuration: winx64_10_perf_bisect
  Benchmark    : media.tough_video_cases
  Metric       : vm_working_set_delta_size/crowd.wav_total
  Change       : 13.21% | 29166.6666667 -> 33018.6666667

Revision             Result                  N
chromium@459649      29166.7 +- 3590.69      9      good
chromium@459650      28659.3 +- 1070.38      6      good
chromium@459651      32986.0 +- 2365.0       6      bad       <--
chromium@459653      33234.0 +- 2912.77      6      bad
chromium@459657      33138.7 +- 1565.32      6      bad
chromium@459664      32963.3 +- 2668.28      6      bad
chromium@459679      33018.7 +- 8731.85      9      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 media.tough_video_cases

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

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


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