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

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


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

android-nexus5

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

=== Auto-CCing suspected CL author neis@chromium.org ===

Hi neis@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 : Georg Neis
  Commit : dabf6003c9def98a3f8e3770b9060989f3ffdd21
  Date   : Tue Oct 24 11:46:38 2017
  Subject: [bigint] Support <, <=, >, >=.

Bisect Details
  Configuration: android_nexus5_perf_bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/load_chrome/load_chrome_blank
  Change       : 0.80% | 1349840.0 -> 1360608.0

Revision                           Result                  N
chromium@511319                    1349840 +- 0.0          6      good
chromium@511338                    1349840 +- 0.0          6      good
chromium@511347                    1349840 +- 0.0          6      good
chromium@511352                    1349840 +- 0.0          6      good
chromium@511352,v8@d75ecf1303      1349840 +- 0.0          6      good
chromium@511352,v8@0105522f7e      1349840 +- 0.0          6      good
chromium@511352,v8@dabf6003c9      1360608 +- 0.0          6      bad       <--
chromium@511353                    1360607 +- 7.30297      6      bad
chromium@511354                    1360608 +- 0.0          6      bad
chromium@511356                    1360608 +- 0.0          6      bad
chromium@511393                    1360608 +- 0.0          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=load.chrome.blank system_health.memory_mobile

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

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


For feedback, file a bug with component Speed>Bisection

Issue 778615 has been merged into this issue.

Issue 778677 has been merged into this issue.

 Issue 779172  has been merged into this issue.

 Issue 780204  has been merged into this issue.

Issue 780248 has been merged into this issue.

A small regression is expected when adding a new primitive to Javascript.