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

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


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

android-nexus6
android-nexus7v2
chromium-rel-mac11-air
chromium-rel-win10

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

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

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_news/load_news_qq

Revision             Result                  N
chromium@511231      2533820 +- 45437.9      21      good
chromium@511286      2532564 +- 59437.2      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=load.news.qq 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/8963949234056112800


For feedback, file a bug with component Speed>Bisection

Regression is too small to bisect.