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

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


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

health-plan-webview-phone

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

=== Auto-CCing suspected CL author zqzhang@google.com ===

Hi zqzhang@google.com, 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 : Zhiqiang Zhang
  Commit : abee192c18a44aae432bb7bff196639204bc10cd
  Date   : Fri May 04 22:33:51 2018
  Subject: Reland "Update gcore to v16.1"

Bisect Details
  Configuration: webview-phone-perf-bisect
  Benchmark    : system_health.webview_startup
  Metric       : webview_startup_cpu_time_avg/load_chrome/load_chrome_blank
  Change       : 1.64% | 304.122888891 -> 309.104666667

Revision                       Result                  N
android-chrome@70a5c38d16      304.123 +- 2.24957      9      good
android-chrome@abee192c18      309.318 +- 2.65109      6      bad       <--
android-chrome@42402a1b3d      308.058 +- 2.07027      9      bad
android-chrome@da329c4b5b      309.105 +- 1.87705      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=load.chrome.blank system_health.webview_startup

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

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


For feedback, file a bug with component Speed>Bisection

Issue 842712 has been merged into this issue.

Assigned, but no owner or component? Please find a component and/or owner