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

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


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

android-webview-nexus6

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

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

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : v8.runtimestats.browsing_mobile
  Metric       : v8-gc-incremental-start_avg/browse_social/browse_social_pinterest_infinite_scroll

Revision             Result                    N
chromium@508702      0.896743 +- 0.839733      21      good
chromium@508757      0.886647 +- 0.740329      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 --story-filter=browse.social.pinterest.infinite.scroll 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/8965499570673777104


For feedback, file a bug with component Speed>Bisection

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

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

This regression has been open for half a year. It's not very actionable and the regression has been in all Chrome user's hands for months.