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

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


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

chromium-rel-mac10

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

===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Roll clang 278861:280106.
Author  : thakis
Commit description:
  
* win: Members of base classes now should show up in debugger.
* win: Debugger shouldn't show funny highlights anymore due to
  debug info no longer including column information.  (we still
  force this on if sanitizers are used, mostly for clusterfuzz.
  maybe we want to make this toggleable independent of sanitizers
  at some point)
* win: -Wextern-initializer no longer warns on midl-generated code
* win: clang-cl now accepts /source-encoding:utf-8 and friends
  (utf-8 was the source enconding in clang-cl before already, but
  now we don't warn on an explicit flag requesting this)
* all platforms: Three plugin checks are now on-by-default,
  remove flags for these (see
    https://codereview.chromium.org/2267713003
    https://codereview.chromium.org/2268203002
    https://codereview.chromium.org/2265093002
  )
* win: clang-cl's /Brepro now does what it's supposed to do
* win: clang-cl now emits absolute paths in diagnostics, by
  popular request.

Ran `tools/clang/scripts/upload_revision.py 280106`.

BUG= 640254 , 637456 , 636109 , 636091 , 636099 

Review-Url: https://codereview.chromium.org/2292173002
Cr-Commit-Position: refs/heads/master@{#415563}
Commit  : a033f395bf2547cf4764f77cc9c86d08f3e22c23
Date    : Wed Aug 31 05:18:36 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev   N  Good?
chromium@415550  41.2784  0.250775  8  good
chromium@415557  41.2777  0.408494  8  good
chromium@415560  41.1637  0.136319  8  good
chromium@415562  41.2802  0.18935   8  good
chromium@415563  42.0814  0.603593  5  bad    <--
chromium@415575  41.9036  0.136823  5  bad
chromium@415599  41.9522  0.38465   5  bad

Bisect job ran on: mac_10_10_perf_bisect
Bug ID: 645586

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests image_decoding.image_decoding_measurement
Test Metric: ImageDecoding_avg/ImageDecoding_avg
Relative Change: 1.74%
Score: 95.0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_10_perf_bisect/builds/2357
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9001970718138909888


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5041676437946368

| 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 Tests>AutoBisect.  Thank you!