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

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


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

perf-monochrome-n-phone

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

=== BISECT JOB RESULTS ===
NO Perf regression found, tests failed to produce values

Bisect Details
  Configuration: monochrome-phone-perf-bisect
  Benchmark    : memory.dual_browser_test
  Metric       : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/on_webview/google_science


To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=google.science memory.dual_browser_test

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

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


For feedback, file a bug with component Speed>Bisection

This regression has been open for half a year. It's not very actionable and the regression has been in all Chrome user's hands for months.