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

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


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

perf-monochrome-n-phone

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

=== 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:gpu:effective_size_avg/on_chrome/http_yandex_ru_touchsearch_text_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=http.yandex.ru.touchsearch.text.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/8946447895144681456


For feedback, file a bug with component Speed>Bisection

Downgrading P2 issues unmodified for more than 6 months, which have no owner or component.