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

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


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

android-nexus5X
android-webview-nexus5X

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

=== Auto-CCing suspected CL author depot-tools-roller@chromium.org ===

Hi depot-tools-roller@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : depot-tools-roller@chromium.org
  Commit : b13a0fb6124ff3bcde0e99ac8d67149bd21d369e
  Date   : Tue Oct 10 18:14:04 2017
  Subject: Roll src/third_party/depot_tools/ e83d02446..9a81700f4 (1 commit)

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/background/after_http_www_baidu_com_s_word_google
  Change       : 3.56% | 39945740.0 -> 41367894.6667

Revision             Result                   N
chromium@507681      39945740 +- 625047       6       good
chromium@507706      40421559 +- 585249       6       good
chromium@507712      40613729 +- 369652       6       good
chromium@507715      40616517 +- 531637       9       good
chromium@507717      40571930 +- 1020316      14      good
chromium@507718      41100346 +- 940504       9       bad       <--
chromium@507730      41141079 +- 755737       6       bad
chromium@507779      41367895 +- 621816       6       bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

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=http.www.baidu.com.s.word.google memory.top_10_mobile

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

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


For feedback, file a bug with component Speed>Bisection

This regression is pretty small and old, and I'm not sure what we can do at this point to figure out why it was caused by the depot_tools roll, so closing.