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

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


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

chromium-rel-win7-gpu-intel

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

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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : performance_browser_tests
  Metric       : TabCapturePerformance_comp_gpu_webrtc/Capture

Revision             Result                  N
chromium@472678      19.3913 +- 1.08007      21      good
chromium@473169      19.3573 +- 1.06355      21      bad

To Run This Test
  .\src\out\Release_x64\performance_browser_tests.exe --test-launcher-print-test-stdio=always --enable-gpu

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

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


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

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

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

Bisect Details
  Configuration: winx64intel_perf_bisect
  Benchmark    : performance_browser_tests
  Metric       : TabCapturePerformance_comp_gpu_webrtc/Capture

Revision             Result                   N
chromium@472678      19.3242 +- 0.767547      21      good
chromium@473169      19.3388 +- 0.692412      21      bad

To Run This Test
  .\src\out\Release_x64\performance_browser_tests.exe --test-launcher-print-test-stdio=always --enable-gpu

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

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


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

Taking this while I'm sorting-out the performance_browser_tests churn. See  bug 709247  and  bug 722367 .

miu: any update on this?

miu: ping? are you still working on this bug? should we kick off more bisects?

Sorry...missed this one. The regression was resolved back at the end of June, at around r482925.