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

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


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

android-webview-nexus6

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

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

Hi kouhei@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 : Kouhei Ueno
  Commit : 2c53cb695bda73713c9addbbb678261d870dadf9
  Date   : Fri Dec 22 11:10:29 2017
  Subject: [ES6 modules] The base url for external classic script should be resource URL

Bisect Details
  Configuration: android_webview_nexus6_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:v8:effective_size_avg/load_search/load_search_baidu
  Change       : 4.72% | 3078357.14286 -> 3238572.85714

Revision             Result                  N
chromium@525968      3078357 +- 272133       14      good
chromium@525972      3053406 +- 7626.69      9       good
chromium@525973      3180093 +- 511090       14      bad       <--
chromium@525974      3217634 +- 634399       21      bad
chromium@525981      3238573 +- 496528       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.baidu 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/8958515350858850128


For feedback, file a bug with component Speed>Bisection

Closing since this seems to have recovered on its own.