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

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


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

android-webview-nexus5X
android-webview-nexus6

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

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

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/browse_shopping/browse_shopping_avito

Revision             Result                 N
chromium@512489      4077324 +- 368415      21      good
chromium@512532      4078153 +- 404343      21      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=browse.shopping.avito 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/8963933751698924848


For feedback, file a bug with component Speed>Bisection

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

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

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

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/load_search/load_search_ebay

Revision             Result                  N
chromium@512512      6198370 +- 61608.8      21      good
chromium@512563      6207244 +- 60924.2      21      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/8963660102240178832


For feedback, file a bug with component Speed>Bisection

=== Auto-CCing suspected CL author huangs@chromium.org ===

Hi huangs@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : Samuel Huang
  Commit : 2cb0922daf3077ef449be6728742e0f5396481b4
  Date   : Mon Oct 30 18:37:00 2017
  Subject: [USB] Exclude usb_ids.* compilation for Chrome under Android.

Bisect Details
  Configuration: android_webview_arm64_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/browse_social/browse_social_instagram
  Change       : 0.18% | 6660144.7619 -> 6671945.14286

Revision             Result                  N
chromium@512512      6660145 +- 56727.7      21      good
chromium@512525      6645614 +- 98163.7      14      good
chromium@512532      6644736 +- 112621       21      good
chromium@512535      6614016 +- 69209.1      6       good
chromium@512537      6631083 +- 13789.2      6       good
chromium@512538      6669702 +- 69729.5      21      bad       <--
chromium@512563      6671945 +- 61741.6      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=browse.social.instagram 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/8963660108225086528


For feedback, file a bug with component Speed>Bisection

These regressions are all < 100kib and not reproducing on bisect. If huangs's CL really is at fault, it's only regressing 30kib, and probably not worth investigating.