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

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


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

perf-go-webview-phone

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

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

Hi wangxianzhu@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 : Xianzhu Wang
  Commit : 976fc1e074a07d78fc4ccb3ab2a9fbd20fd9ce69
  Date   : Fri Apr 27 03:05:06 2018
  Subject: [SPv175+] Don't create a new chunk with different id and the same properties.

Bisect Details
  Configuration: go-webview-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:cc:effective_size_avg/load_tools/load_tools_weather
  Change       : 58.98% | 5160384.0 -> 8203788.0

Revision                                       Result                  N
android-chrome@7efa2ba1f1                      5160384 +- 80264.9      6      good
android-chrome@972eebff76                      5160384 +- 80264.9      6      good
android-chrome@4e4cf7775f                      5127616 +- 101528       6      good
android-chrome@5e7f0484c1                      5193152 +- 124346       6      good
android-chrome@5e7f0484c1,chromium@554232      5193152 +- 124346       6      good
android-chrome@5e7f0484c1,chromium@554266      5160384 +- 80264.9      6      good
android-chrome@5e7f0484c1,chromium@554276      5193152 +- 0.0          6      good
android-chrome@5e7f0484c1,chromium@554279      5160384 +- 80264.9      6      good
android-chrome@5e7f0484c1,chromium@554280      5160384 +- 80264.9      6      good
android-chrome@5e7f0484c1,chromium@554281      7940840 +- 101528       6      bad       <--
android-chrome@5e7f0484c1,chromium@554282      8006376 +- 101528       6      bad
android-chrome@5e7f0484c1,chromium@554288      7854263 +- 272591       6      bad
android-chrome@5e7f0484c1,chromium@554305      7713876 +- 258784       6      bad
android-chrome@452ccfa0f7                      7713876 +- 336118       6      bad
android-chrome@0f6680b944                      7844144 +- 358292       6      bad
android-chrome@efed3974e3                      7876108 +- 213614       6      bad
android-chrome@d3db009934                      7941644 +- 236246       6      bad
android-chrome@061a8220c9                      8203788 +- 741678       6      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.tools.weather 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/8947464658822832496


For feedback, file a bug with component Speed>Bisection