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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgi92L6AgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg6_n1swkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg66KhsQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg68H-pgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg68GltwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg69b9_gkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg672PtwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg65euqwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg66K1qAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg6_38vwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg6_CwtwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg6_6w5wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg65GmvgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg68GltwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg6-C8pQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg65y4vAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg64L_vAkM


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

android-nexus7v2

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

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


===== SUSPECTED CL(s) =====
Subject : Pass correct texture hint for GPU raster
Author  : ericrk
Commit description:
  
Currently, ResourcePool creates all resources with
ResourceProvider::TEXTURE_HINT_IMMUTABLE. This is fine for SW raster,
however we should be using TEXTURE_HINT_IMMUTABLE_FRAMEBUFFER for GPU
raster. Using the correct flag passes additional information to ANGLE
via a GL extension and causes us to skip an unnecessary texture copy.

R=vmpstr
CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_trusty_blink_rel

Review-Url: https://codereview.chromium.org/2507963003
Cr-Commit-Position: refs/heads/master@{#433437}
Commit  : da59d418f54604ba2451cd0ef3a9cd42c05ca530
Date    : Sun Nov 20 00:45:40 2016


===== TESTED REVISIONS =====
Revision         Mean    Std Dev  N  Good?
chromium@433312  1015.5  57.81    8  good
chromium@433382  964.5   234.908  8  good
chromium@433417  981.0   236.356  8  good
chromium@433435  969.5   249.411  8  good
chromium@433436  961.5   223.495  8  good
chromium@433437  1554.4  222.25   5  bad    <--
chromium@433438  1599.2  28.5096  5  bad
chromium@433440  1564.0  225.566  5  bad
chromium@433444  1600.0  24.6577  5  bad
chromium@433452  1544.0  210.751  5  bad

Bisect job ran on: android_nexus7_perf_bisect
Bug ID: 669302

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=video.html.src.tulip2.mp4 media.android.tough_video_cases
Test Metric: vm_shared_dirty_delta/video.html?src_tulip2.mp4
Relative Change: 52.04%

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus7_perf_bisect/builds/3516
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8994701612758799792


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

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