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

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


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

android-one

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

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

Bisect Details
  Configuration: android_one_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:private_dirty_size_avg/foreground/http_search_yahoo_com_search__ylt_p_google

Revision             Result                  N
chromium@487823      29042613 +- 299685      21      good
chromium@487900      29191044 +- 847043      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/8973189471050402272


For feedback, file a bug with component Speed>Bisection

Kicked wider bisect.

Bisect can't repro.