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

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


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

android-webview-nexus6

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

All metrics have recovered.

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

Hi fsamuel@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 : Fady Samuel
  Commit : 3a98969d6314273682418cfd65d58496cc8ba88d
  Date   : Wed Nov 15 02:10:22 2017
  Subject: Surface synchronization: Move surface scaling to SurfaceAggregator

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : thread_times.key_silk_cases
  Metric       : thread_browser_cpu_time_per_frame/http___jsfiddle.net_R8DX9_4_show_
  Change       : 21.83% | 1.4765960452 -> 1.79896592183

Revision             Result                    N
chromium@516491      1.4766 +- 0.0285818       6      good
chromium@516528      1.49471 +- 0.0332755      6      good
chromium@516546      1.48992 +- 0.0261707      6      good
chromium@516555      1.4991 +- 0.0250724       6      good
chromium@516558      1.49758 +- 0.0523656      6      good
chromium@516559      1.49046 +- 0.0747332      6      good
chromium@516560      1.80913 +- 0.0553883      6      bad       <--
chromium@516564      1.79897 +- 0.0391602      6      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 --story-filter=http...jsfiddle.net.R8DX9.4.show. thread_times.key_silk_cases

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8962733897493871760


For feedback, file a bug with component Speed>Bisection

Not sure why this bug was reopened if all metrics have recovered. I think it's because it was reopened automatically after the bisect finished. Marking as WontFix again.