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

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


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

android-nexus5X
android-one
android-webview-nexus5X

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

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

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : v8-gc-latency-mark-compactor_sum/browse_news/browse_news_washingtonpost

Revision             Result                  N
chromium@513738      4.96633 +- 7.98121      21      good
chromium@513765      5.5261 +- 9.63703       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.news.washingtonpost 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/8962666431790356240


For feedback, file a bug with component Speed>Bisection

Closing as not reproducible.