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

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


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

perf-go-webview-phone

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

=== 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_os:gpu_memory:proportional_resident_size_avg/load_tools/load_tools_weather
  Change       : 23.24% | 19173716.6667 -> 23630164.6667

Revision                                       Result                   N
android-chrome@7efa2ba1f1                      19173717 +- 298875       6      good
android-chrome@972eebff76                      19174399 +- 167294       6      good
android-chrome@4e4cf7775f                      19141631 +- 197177       6      good
android-chrome@5e7f0484c1                      19135487 +- 104642       6      good
android-chrome@5e7f0484c1,chromium@554232      19311615 +- 271001       6      good
android-chrome@5e7f0484c1,chromium@554266      19302058 +- 144235       6      good
android-chrome@5e7f0484c1,chromium@554276      19443370 +- 238762       6      good
android-chrome@5e7f0484c1,chromium@554279      19214677 +- 260844       6      good
android-chrome@5e7f0484c1,chromium@554280      19265877 +- 359454       6      good
android-chrome@5e7f0484c1,chromium@554281      24994815 +- 1476719      6      bad       <--
android-chrome@5e7f0484c1,chromium@554282      24458922 +- 2294712      6      bad
android-chrome@5e7f0484c1,chromium@554288      24594090 +- 1889552      6      bad
android-chrome@5e7f0484c1,chromium@554305      25069909 +- 1549905      6      bad
android-chrome@452ccfa0f7                      23924394 +- 1939960      6      bad
android-chrome@0f6680b944                      24095743 +- 2516527      6      bad
android-chrome@efed3974e3                      23935999 +- 2343344      6      bad
android-chrome@d3db009934                      24680106 +- 1815779      6      bad
android-chrome@061a8220c9                      23630165 +- 2099007      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/8947464685773719296


For feedback, file a bug with component Speed>Bisection