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

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


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

android-nexus6

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

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

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/foreground/https_www_google_co_uk_hl_en_q_science

Revision             Result                  N
chromium@488182      37085516 +- 777943      21      good
chromium@488241      37167698 +- 940001      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/8973189499153376912


For feedback, file a bug with component Speed>Bisection

The graphs are pretty noisy and bisect can't repro.