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

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


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

android-nexus7v2

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

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

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/load_search/load_search_ebay

Revision             Result                  N
chromium@487676      18438382 +- 368528      21      good
chromium@487765      18410428 +- 394588      20      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=load.search.ebay 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/8973189793308992640


For feedback, file a bug with component Speed>Bisection

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

=== 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_nexus5X_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/browse_shopping/browse_shopping_avito
  Change       : 2.56% | 59939041.1429 -> 61475187.4286

Suspected Commit Range
  12 commits in range
  https://chromium.googlesource.com/chromium/src/+log/4afd513b88234976f17b06eee24892ce9d149e7e..e5ef88bfc930b8066ae7c8a5ec5cf35577bbcd2b


Revision                           Result                   N
chromium@485946                    59939041 +- 3180659      14       good
chromium@486391                    59384301 +- 1665414      6        good
chromium@486630                    59846751 +- 1866415      9        good
chromium@486741                    59383887 +- 3539144      14       good
chromium@486745                    59437793 +- 4081839      14       good
chromium@486745,v8@44cce0fcc0      ---                      ---      build failure
---                                ---                      ---      too many build failures to list
chromium@486745,v8@a97abb909b      ---                      ---      build failure
chromium@486746                    61058883 +- 1557088      6        bad
chromium@486747                    60682335 +- 2211835      9        bad
chromium@486748                    61028788 +- 3394001      9        bad
chromium@486755                    60718744 +- 2890279      14       bad
chromium@486769                    61377404 +- 2468763      9        bad
chromium@486797                    60988275 +- 3866029      14       bad
chromium@486853                    61361597 +- 3807884      14       bad
chromium@487758                    61475187 +- 4102879      14       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.shopping.avito 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/8968440492314271264


For feedback, file a bug with component Speed>Bisection

This is a small regression and most of these graphs present newer regressions associated to different bugs - maybe mark WontFix?

+1