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

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


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

perf-monochrome-n-phone

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

=== 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:webview:all_processes:reported_by_chrome:v8:allocated_objects_size_avg/on_chrome/https_m_facebook_com_rihanna


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=https.m.facebook.com.rihanna 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/8945556672915240688


For feedback, file a bug with component Speed>Bisection