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

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


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

android-nexus5X

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

=== BISECT JOB RESULTS ===
NO Perf regression found

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/browse_media/browse_media_youtube

Revision             Result                   N
chromium@524620      62850935 +- 3506850      21      good
chromium@524629      63260583 +- 3065736      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-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.media.youtube 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/8959563217411639408


For feedback, file a bug with component Speed>Bisection

 Issue 797029  has been merged into this issue.

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/12cff59a840000

Trying a wider bisect, but the graph is really noisy so this looks like it will be pretty difficult to track down.

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12cff59a840000

Roll src/third_party/catapult/ 6c84ef000..8a4ac91dd (1 commit)
By catapult-deps-roller@chromium.org · Mon Dec 18 13:51:46 2017
chromium @ 97b283f950a14bad9ff01b8a47911531589fba40

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

+mlamouri, perezju: This test regressed at "Disable autoplay restrictions on Chrome via command line flag" in catapult. I'm closing as WontFix because I think there are now videos in the test which make it more realistic but also take up more memory. Feel free to reopen if this is not working as intended.

Mounir was working on a CL for this on  issue 797065 . Not sure if we still want that?