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

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


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

android-nexus7v2
android-webview-nexus6
chromium-rel-win7-dual
linux-release

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

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

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


Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : total:500ms_window:renderer_eqt:v8:gc_max/total:500ms_window:renderer_eqt:v8:gc_max


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 v8.browsing_mobile

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

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


For feedback, file a bug with component Speed>Bisection

Think this is the same underlying issue as  crbug.com/785721 

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.