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

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


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

linux-release

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

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

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

Revision             Result                    N
chromium@488912      16.6683 +- 0.0279762      21      good
chromium@488973      16.6716 +- 0.0859823      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/8972275673804239712


For feedback, file a bug with component Speed>Bisection

ref build jumps too.