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

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


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

android-webview-nexus6

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/load_search/load_search_ebay
  Change       : 1.25% | 22418673.7143 -> 22579514.8571

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/6cff7e77ad345f90dcc46b106620baf4cab3cef8..1739c42dd9346a595a82600a558852b37535ba39


Revision             Result                  N
chromium@499406      22418674 +- 641803      14       good
chromium@499409      22392342 +- 609853      14       good
chromium@499410      ---                     ---      build failure
chromium@499411      22632470 +- 261915      14       bad
chromium@499412      22579515 +- 241815      14       bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

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.search.ebay system_health.memory_mobile

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

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


For feedback, file a bug with component Speed>Bisection

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

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

Suspected Commit
  Author : Jeremy Roman
  Commit : 1739c42dd9346a595a82600a558852b37535ba39
  Date   : Sun Sep 03 03:07:35 2017
  Subject: [Bindings] Generate explicit constructor stubs.

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/load_search/load_search_ebay
  Change       : 2.22% | 22186884.0 -> 22634152.5714

Revision             Result                  N
chromium@499244      22186884 +- 141297      6       good
chromium@499333      22371887 +- 344572      6       good
chromium@499377      22358843 +- 595377      14      good
chromium@499399      22451369 +- 791714      21      good
chromium@499410      22472873 +- 515949      14      good
chromium@499411      22650756 +- 312587      9       bad       <--
chromium@499412      22700591 +- 148975      6       bad
chromium@499413      22793775 +- 273872      6       bad
chromium@499416      22662816 +- 289348      9       bad
chromium@499421      22634153 +- 311111      14      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

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.search.ebay system_health.memory_mobile

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

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


For feedback, file a bug with component Speed>Bisection