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

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


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

android-webview-nexus5X

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

=== 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_chrome:malloc:effective_size_avg/load_news/load_news_cnn

Revision             Result                   N
chromium@486846      46378872 +- 5938178      21      good
chromium@486914      46626557 +- 5102387      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=load.news.cnn 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/8973652672980209344


For feedback, file a bug with component Speed>Bisection

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

=== 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_chrome:malloc:effective_size_avg/load_news/load_news_cnn
  Change       : 2.57% | 45180509.2143 -> 46341290.1429

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


Revision                           Result                   N
chromium@486438                    45180509 +- 3357761      14       good
chromium@486724                    44550924 +- 3064035      9        good
chromium@486742                    44732347 +- 3576981      14       good
chromium@486745                    44347555 +- 1754329      6        good
chromium@486745,v8@44cce0fcc0      ---                      ---      build failure
---                                ---                      ---      too many build failures to list
chromium@486745,v8@a97abb909b      ---                      ---      build failure
chromium@486746                    46470495 +- 1715247      6        bad
chromium@486747                    45962405 +- 3288739      14       bad
chromium@486751                    45920110 +- 5291314      21       bad
chromium@486760                    46366155 +- 4749103      14       bad
chromium@486796                    45834583 +- 2563185      14       bad
chromium@486867                    46189720 +- 4700015      14       bad
chromium@487009                    46341290 +- 3835920      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.news.cnn 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/8973570461612955200


For feedback, file a bug with component Speed>Bisection

This happens in the v8 roll below.
https://chromium.googlesource.com/v8/v8/+log/a29b8877..a97abb90

machenbach, I'd tentatively assign you to this since you submitted one CL in the rolled v8 range. Could you reassign people who is better to investigate this?

-> performance or memory sheriff
If the output above is reliable, we're talking about:
https://chromium.googlesource.com/v8/v8/+log/a29b8877..a97abb90

+ nednguyen for failed bisect into V8

Annie, the blocked-on bug looks like a mistake?

Whoops, thanks!

doesn't look like there's much we can do about this: the build fails testing the v8 changes.