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

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


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

android-nexus5
android-nexus5X
android-nexus7v2
android-one
chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual
chromium-rel-win8-dual
linux-release
win-high-dpi

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

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

Hi bmeurer@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 : Benedikt Meurer
  Commit : 2b4cc835f14cfd1d195f4f8729140a01b5e22f8d
  Date   : Fri Jan 05 08:26:01 2018
  Subject: [builtins] Port EnqueueMicrotask to CSA.

Bisect Details
  Configuration: android_nexus5X_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.71% | 1109864.0 -> 1128788.0

Revision                           Result              N
chromium@527266                    1109864 +- 0.0      6      good
chromium@527274                    1109864 +- 0.0      6      good
chromium@527276                    1109864 +- 0.0      6      good
chromium@527276,v8@204441b230      1109864 +- 0.0      6      good
chromium@527276,v8@2b4cc835f1      1128788 +- 0.0      6      bad       <--
chromium@527276,v8@a97298bae5      1128788 +- 0.0      6      bad
chromium@527277                    1128788 +- 0.0      6      bad
chromium@527278                    1128788 +- 0.0      6      bad
chromium@527281                    1128788 +- 0.0      6      bad
chromium@527295                    1128788 +- 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/8957877045704667584


For feedback, file a bug with component Speed>Bisection