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

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


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

chromium-rel-mac12
chromium-rel-mac12-mini-8gb

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

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

Bisect Details
  Configuration: mac_10_12_perf_bisect
  Benchmark    : smoothness.gpu_rasterization_and_decoding.image_decoding_cases
  Metric       : frame_times/yuv_decoding.html

Revision             Result                    N
chromium@489389      16.6834 +- 0.0607804      21      good
chromium@489553      16.7491 +- 1.12658        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=yuv.decoding.html smoothness.gpu_rasterization_and_decoding.image_decoding_cases

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8972811911030814816


For feedback, file a bug with component Speed>Bisection

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

Kicked another bisect for smoothness.gpu_rasterization_and_decoding.image_decoding_cases / mean_frame_time /

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

Bisect Details
  Configuration: mac_10_12_perf_bisect
  Benchmark    : smoothness.gpu_rasterization_and_decoding.image_decoding_cases
  Metric       : mean_frame_time/yuv_decoding.html

Revision             Result                    N
chromium@489389      16.6866 +- 0.0230899      21      good
chromium@489553      16.6869 +- 0.0112504      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=yuv.decoding.html smoothness.gpu_rasterization_and_decoding.image_decoding_cases

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8972546719279863488


For feedback, file a bug with component Speed>Bisection

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

Trying one more bisect on a different bot/wider range. Not sure what can be done if that doesn't find the culprit.

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

Bisect Details
  Configuration: mac_10_12_mini_8gb_perf_bisect
  Benchmark    : smoothness.image_decoding_cases
  Metric       : frame_times/yuv_decoding.html

Revision             Result                   N
chromium@489264      16.7315 +- 0.80301       21      good
chromium@489726      16.7021 +- 0.239445      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=yuv.decoding.html smoothness.image_decoding_cases

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8970613483639850624


For feedback, file a bug with component Speed>Bisection

Doesn't look like we'll be able to track this down.