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

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


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

android-webview-nexus5X

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

=== 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:native_heap:proportional_resident_size_avg/browse_media/browse_media_flickr_infinite_scroll

Revision             Result                   N
chromium@486303      79769807 +- 2644625      21      good
chromium@486368      79909705 +- 2912764      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.media.flickr.infinite.scroll 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/8973799877947060160


For feedback, file a bug with component Speed>Bisection

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

Kicked with larger range.

=== 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_arm64_aosp_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:webview:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/browse_media/browse_media_flickr_infinite_scroll
  Change       : 3.05% | 79156674.6667 -> 81524617.7778

Suspected Commit Range
  12 commits in range
  https://chromium.googlesource.com/chromium/src/+log/4afd513b88234976f17b06eee24892ce9d149e7e..e5ef88bfc930b8066ae7c8a5ec5cf35577bbcd2b


Revision                           Result                   N
chromium@486157                    79156675 +- 2503833      9        good
chromium@486468                    80049830 +- 1931212      9        good
chromium@486623                    79985546 +- 2023808      9        good
chromium@486701                    80149158 +- 1679603      9        good
chromium@486740                    80069741 +- 907038       6        good
chromium@486745                    80396739 +- 939461       6        good
chromium@486745,v8@44cce0fcc0      ---                      ---      build failure
---                                ---                      ---      too many build failures to list
chromium@486745,v8@a97abb909b      ---                      ---      build failure
chromium@486746                    81855256 +- 2069629      6        bad
chromium@486747                    81595501 +- 1839895      9        bad
chromium@486748                    81883928 +- 933846       6        bad
chromium@486750                    81586627 +- 1268321      6        bad
chromium@486759                    81916355 +- 2477875      6        bad
chromium@486778                    81524618 +- 2587297      9        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.media.flickr.infinite.scroll 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/8973177890531997904


For feedback, file a bug with component Speed>Bisection

Only happened on one device/page, no ref build, graph is really noisy, and builds fail so it can't be narrowed down.