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

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


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

android-nexus7v2

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

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

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/foreground/http_search_yahoo_com_search__ylt_p_google

Revision             Result                   N
chromium@485814      24882237 +- 982771       21      good
chromium@485894      24951966 +- 1145059      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/8973189251820787872


For feedback, file a bug with component Speed>Bisection

This graph is really noisy, comes back down eventually, and bisect can't repro.