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

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


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

android-one

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

=== 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_one_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/load_media/load_media_facebook_photos
  Change       : 0.13% | 14423381.5385 -> 14442817.1429

Suspected Commit Range
  3 commits in range
  https://chromium.googlesource.com/chromium/src/+log/d5cf29a85fff3fd471d9223fe05cd112c09debbb..4e73667e969ab09fce17821c620f232ee28e53d6


Revision             Result                   N
chromium@514613      14423382 +- 104714       13       good
chromium@514655      14433354 +- 89283.4      20       good
chromium@514656      ---                      ---      build failure
chromium@514657      ---                      ---      build failure
chromium@514658      14465114 +- 467819       20       bad
chromium@514659      14444747 +- 73468.7      20       bad
chromium@514661      14442911 +- 64760.4      14       bad
chromium@514665      14449088 +- 45058.7      14       bad
chromium@514678      14443156 +- 74896.4      14       bad
chromium@514700      14440026 +- 112681       20       bad
chromium@514785      14442817 +- 92443.7      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-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.media.facebook.photos 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/8961038769159421008


For feedback, file a bug with component Speed>Bisection