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

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


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

android-nexus5
android-nexus5X
android-nexus6
android-nexus7v2

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

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

Hi jkummerow@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 : Jakob Kummerow
  Commit : 1560988249c97c5cc1763aa364a0423f9e318c13
  Date   : Wed Oct 11 17:36:53 2017
  Subject: [bigint] Support BigInts in <<,>>,>>>,&,|,^ binary ops

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       : 1.42% | 1634168.0 -> 1657344.0

Revision                           Result              N
chromium@508852                    1634168 +- 0.0      6      good
chromium@508862                    1634168 +- 0.0      6      good
chromium@508867                    1634168 +- 0.0      6      good
chromium@508869                    1634168 +- 0.0      6      good
chromium@508870                    1634168 +- 0.0      6      good
chromium@508870,v8@dabd1c0af8      1639584 +- 0.0      6      good
chromium@508870,v8@83103bce13      1639584 +- 0.0      6      good
chromium@508870,v8@6576495f3a      1639584 +- 0.0      6      good
chromium@508870,v8@1560988249      1653008 +- 0.0      6      bad       <--
chromium@508870,v8@d567f413c7      1653008 +- 0.0      6      bad
chromium@508870,v8@61a23faa52      1653008 +- 0.0      6      bad
chromium@508870,v8@126b2bd281      1653936 +- 0.0      6      bad
chromium@508871                    1657280 +- 0.0      6      bad
chromium@508889                    1657280 +- 0.0      6      bad
chromium@508925                    1657344 +- 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/8965499936656824288


For feedback, file a bug with component Speed>Bisection