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

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


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

android-nexus5

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

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

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:private_dirty_size_avg/background/after_http_www_amazon_com_gp_aw_s_k_nexus

Revision             Result                   N
chromium@487872      51002141 +- 1801892      21      good
chromium@488097      50892913 +- 4927870      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 memory.top_10_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8973189111157746608


For feedback, file a bug with component Speed>Bisection

These graphs constantly jump up and down.