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

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


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

android-nexus6

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

=== 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:java_heap:proportional_resident_size_avg/load_chrome/load_chrome_blank
  Change       : 1.21% | 15839451.4286 -> 15974741.3333

Suspected Commit Range
  2 commits in range
  https://chromium.googlesource.com/chromium/src/+log/4e5ecdce95c6989b948f2c0febc23400fe99aad8..3ccc5d6b68e1d223b88cab57b549adfd2b353457


Revision             Result                   N
chromium@488346      15839451 +- 212510       14       good
chromium@488347      ---                      ---      build failure
chromium@488348      15898819 +- 142256       21       bad
chromium@488352      15898673 +- 156712       21       bad
chromium@488355      15893138 +- 296969       14       bad
chromium@488364      15905109 +- 94526.5      6        bad
chromium@488382      15877291 +- 67341.8      6        bad
chromium@488417      15907499 +- 90907.5      6        bad
chromium@488487      15974741 +- 119704       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=load.chrome.blank 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/8973191213554124272


For feedback, file a bug with component Speed>Bisection

Bisect only reproed a 50kib change, and can't narrow, and this bug is pretty old.