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

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


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

android-nexus6

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

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

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : v8.browsing_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/browse_news/browse_news_washingtonpost

Revision             Result                   N
chromium@519629      12681426 +- 1949768      21      good
chromium@519680      12542676 +- 2209366      21      bad

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.news.washingtonpost v8.browsing_mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8960969789792961456


For feedback, file a bug with component Speed>Bisection

Flaky, within range