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

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


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

android-webview-nexus5X

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

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

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

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : kraken
  Metric       : Total/Total

Revision             Result                  N
chromium@468722      4601.67 +- 1144.71      21      good
chromium@468785      4576.76 +- 1051.46      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests kraken

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8980446933571784464

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5774802595348480


| 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 Speed>Bisection.  Thank you!

=== BISECT JOB RESULTS ===
Bisect failed for unknown reasons

Please contact the team (see below) and report the error.


Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : kraken
  Metric       : Total/Total


To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests kraken

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8980446919079547600

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6462314066214912


| 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 Speed>Bisection.  Thank you!

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

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

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

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : kraken
  Metric       : Total/Total

Revision             Result                  N
chromium@468722      4601.67 +- 1144.71      21      good
chromium@468785      4576.76 +- 1051.46      21      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests kraken

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8980405504255216752

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5774802595348480


| 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 Speed>Bisection.  Thank you!

=== Auto-CCing suspected CL author dcastagna@chromium.org ===

Hi dcastagna@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : dcastagna
  Commit : 00ef929f434505f4d09a130e0bc1d4a4938d490f
  Date   : Tue May 02 21:56:23 2017
  Subject: ozone: Wait on EGLFence before committing buffers. Avoid using GL.

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : kraken
  Metric       : Total/Total
  Change       : 1.64% | 4537.4 -> 4462.87142857

Revision             Result                  N
chromium@468722      4537.4 +- 468.338       14      good
chromium@468754      4559.14 +- 303.527      9       good
chromium@468770      4591.06 +- 584.595      14      good
chromium@468778      4582.0 +- 823.349       21      good
chromium@468782      4645.14 +- 708.181      9       good
chromium@468784      4628.3 +- 585.458       9       good
chromium@468785      4462.87 +- 96.4869      14      bad       <--

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests kraken

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8980405498381913664

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=6462314066214912


| 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 Speed>Bisection.  Thank you!

Are you suggesting crrev.com/2858693002 is causing a regression on Android?

crrev.com/2858693002 is completely contained in ui/ozone code, more specifically, ozone drm code. Android is not using that code at all.

graphs recovered