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

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


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

android-nexus6

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

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

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/browse_tools/browse_tools_maps

Revision             Result                    N
chromium@487676      178553447 +- 2817611      21      good
chromium@487754      178506538 +- 2530195      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 --story-filter=browse.tools.maps 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/8973194456279456256


For feedback, file a bug with component Speed>Bisection

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

Clicked off a bisect with a larger range.

=== 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_nexus6_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/browse_tools/browse_tools_maps
  Change       : 1.14% | 176416749.333 -> 178420717.333

Suspected Commit Range
  6 commits in range
  https://chromium.googlesource.com/chromium/src/+log/2a17bfdfaba69be381c18c170553cd165062dde4..7891182716ec2c31a7e216d830c4e6f827a778d5


Revision             Result                    N
chromium@486073      176416749 +- 1034351      6        good
chromium@486506      176985980 +- 1407009      9        good
chromium@486722      177237528 +- 1879516      8        good
chromium@486749      177924541 +- 2881827      14       good
chromium@486760      178025697 +- 1953345      14       good
chromium@486761      ---                       ---      build failure
chromium@486762      ---                       ---      build failure
chromium@486763      ---                       ---      build failure
chromium@486764      ---                       ---      build failure
chromium@486765      ---                       ---      build failure
chromium@486766      178707535 +- 2222789      14       bad
chromium@486769      178558275 +- 2889398      21       bad
chromium@486776      178775631 +- 2505603      14       bad
chromium@486830      178975896 +- 1737995      6        bad
chromium@486938      178499452 +- 2198431      9        bad
chromium@487803      178420717 +- 824742       6        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=browse.tools.maps 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/8973184342554492416


For feedback, file a bug with component Speed>Bisection

Only found on one device/page, bisect can't repro.