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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg3u2MvQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg3rewvAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnpGnrgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnpvW8AkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDg7u6WiwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnqqzuQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgnv2ZtgoM


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

android-nexus5
android-webview-nexus5X
android-webview-nexus6

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

=== 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_nexus5_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/background_news/background_news_nytimes
  Change       : 7.46% | 64305938.2857 -> 69100081.2308

Suspected Commit Range
  3 commits in range
  https://chromium.googlesource.com/chromium/src/+log/ee4d4d912c63490b2fd87eded9f10006a46e49e2..579d7f54029f25dd67141765262594c3a37564cb


Revision             Result                    N
chromium@483434      64305938 +- 17871477      14       good
chromium@483513      62977664 +- 18445471      14       good
chromium@483516      63030833 +- 17894228      13       good
chromium@483517      63039177 +- 19269076      14       good
chromium@483518      ---                       ---      build failure
chromium@483519      ---                       ---      build failure
chromium@483520      69182738 +- 6286125       14       bad
chromium@483525      68752293 +- 5455594       14       bad
chromium@483537      69728782 +- 4864363       9        bad
chromium@483560      69100081 +- 5331134       13       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-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=background.news.nytimes 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/8974917872778184496


For feedback, file a bug with component Speed>Bisection

pdr: sorry for the late notice here, but I'm cleaning up old perfbot bugs and found this one where the bisect failed because the build was broken from r483518 to r483520, but it looks pretty clear that r483520 is the culprit here: it reverts r482782, and the metrics drop at the land and jump at the revert. So looks like that CL was a memory-performance tradeoff. I'm WontFix-ing, but feel free to reopen or work on this in a new bug if you want to investigate further.