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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg5MzOowoM


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

android-webview-nexus5X

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

=== 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    : memory.top_10_mobile
  Metric       : memory:webview:all_processes:reported_by_chrome:v8:effective_size_avg/foreground/https_mobile_twitter_com_justinbieber_skip_interstitial_true
  Change       : 2.55% | 7284187.55556 -> 7476245.33333

Suspected Commit Range
  2 commits in range
  Mismatching LKGR/FKBR depots, unable to provide handy url.
  good_revision: chromium@6dd692b945fc8599a4c7db22854d19c9b27d0d4c
  bad_revision : v8@c9b4087f4a00632b7133c491addac7272d45cbef


Revision                           Result                  N
chromium@454234                    7284188 +- 216722       9        good
chromium@454239                    7329812 +- 352313       9        good
chromium@454240                    7344940 +- 303592       9        good
chromium@454240,v8@eda659cc5e      ---                     ---      build failure
chromium@454240,v8@c9b4087f4a      7465671 +- 174612       9        bad
chromium@454241                    7436572 +- 77412.1      9        bad
chromium@454243                    7487854 +- 247914       9        bad
chromium@454251                    7476245 +- 109790       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 memory.top_10_mobile

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8986187099914475808

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5851027716177920


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!

hablich: looks like the v8 roll at https://codereview.chromium.org/2728453005 regressed memory by ~100kb. But the exact change that regressed fails to build, so can't be narrowed down. Can you help triage?

That was a roll-back because of M58. It seems the improvement was done in the range of https://chromium.googlesource.com/v8/v8/+log/03d03326..0096d404.

We have already rolled that in so I assume that this is going to be fixed when the bots have caught up.