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

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


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

android-nexus5
android-nexus7v2
android-webview-nexus5X
chromium-rel-win8-dual

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

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

Suspected Commit
  Author : Sayaka Takayama
  Commit : 06a6739f10dd81842f4a54509f34519a4f769fa0
  Date   : Wed Sep 20 04:25:13 2017
  Subject: v8binding: changed FrameRequestCallback from callback interface to callback function

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-incremental-finalize_avg/browse_social/browse_social_instagram
  Change       : 73.35% | 0.236416666667 -> 0.409833333333

Revision             Result                     N
chromium@503020      0.236417 +- 0.0307564      6      good
chromium@503042      0.242542 +- 0.0440616      6      good
chromium@503045      0.227625 +- 0.0139989      6      good
chromium@503047      0.241125 +- 0.0225187      6      good
chromium@503048      0.398644 +- 0.161096       6      bad       <--
chromium@503053      0.414028 +- 0.249375       6      bad
chromium@503064      0.409833 +- 0.0647508      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=browse.social.instagram v8.runtimestats.browsing_mobile

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

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


For feedback, file a bug with component Speed>Bisection