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

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


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

android-nexus5

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4311
Failure reason: the build has failed due to infrastructure failure.

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

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


===== SUSPECTED CL(s) =====
Subject : Remove runtime flag 'UnsafeES3APIs' from blink webgl.
Author  : yunchao.he
Commit description:
  
This is the first step to remove unsafe mode and enable
ES3 APIs for WebGL2 and ES3 context by default.
Command line option "--enable-unsafe-es3-apis" would be
unnecessary and removed afterwards.

Intent to implement:
https://www.chromestatus.com/features/6694359164518400

Launch bug:
http://crbug.com/641635
(Note that this is not the launch CL -- it's still not possible to create a WebGL 2.0 context without the flag)

BUG= 654787 , 641635
CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.win:win_optional_gpu_tests_rel;master.tryserver.chromium.mac:mac_optional_gpu_tests_rel

Review-Url: https://codereview.chromium.org/2451943002
Cr-Commit-Position: refs/heads/master@{#428253}
Commit  : 58dd74648c572ceaf28175b2a2802d3c50a9b316
Date    : Fri Oct 28 02:27:13 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@428235  44268.0  1541.93  5  good
chromium@428251  43716.0  1205.14  5  good
chromium@428252  45915.2  3012.88  5  good
chromium@428253  61328.8  4868.2   5  bad    <--
chromium@428255  63346.4  3002.63  5  bad
chromium@428259  60066.4  1544.89  5  bad
chromium@428267  63045.6  5427.28  5  bad
chromium@428298  64708.0  4413.81  5  bad

Bisect job ran on: android_nexus5_perf_bisect
Bug ID: 661493

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests indexeddb_perf
Test Metric: vm_private_dirty_final_renderer/vm_private_dirty_final_renderer
Relative Change: 46.17%
Score: 99.8

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4318
Job details: https://chromeperf.appspot.com/buildbucket_job_status/8997056798834770208


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

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

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

Bisect failed: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/4852
Failure reason: the build has failed due to infrastructure failure.