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

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


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

perf-monochrome-n-phone

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

=== 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_os:system_memory:private_footprint_size_avg/on_chrome/https_mobile_twitter_com_justinbieber_skip_interstitial_true


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.mobile.twitter.com.justinbieber.skip.interstitial.true 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/8947447434171225712


For feedback, file a bug with component Speed>Bisection

This recovered.