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

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


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

android-nexus5X

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

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

Suspected Commit
  Author : Georg Neis
  Commit : dabf6003c9def98a3f8e3770b9060989f3ffdd21
  Date   : Tue Oct 24 11:46:38 2017
  Subject: [bigint] Support <, <=, >, >=.

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/foreground/https_mobile_twitter_com_justinbieber_skip_interstitial_true
  Change       : 2.12% | 2833429.33333 -> 2893442.0

Revision                           Result                  N
chromium@511331                    2833429 +- 225.542      6      good
chromium@511343                    2833385 +- 227.027      6      good
chromium@511349                    2833499 +- 231.217      6      good
chromium@511352                    2833419 +- 267.816      6      good
chromium@511352,v8@d75ecf1303      2833366 +- 227.807      6      good
chromium@511352,v8@0105522f7e      2833365 +- 209.584      6      good
chromium@511352,v8@dabf6003c9      2844082 +- 219.873      6      bad       <--
chromium@511353                    2844051 +- 210.479      6      bad
chromium@511354                    2844155 +- 86.7948      6      bad
chromium@511355                    2844075 +- 231.546      6      bad
chromium@511378                    2844128 +- 166.853      6      bad
chromium@511424                    2893442 +- 85338.3      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=https.mobile.twitter.com.justinbieber.skip.interstitial.true 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/8964185865938340096


For feedback, file a bug with component Speed>Bisection