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

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


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

linux-perf
mac-10_12_laptop_low_end-perf
mac-10_13_laptop_high_end-perf

memory.desktop - Benchmark documentation link:
  None

system_health.memory_desktop - Benchmark documentation link:
  https://bit.ly/system-health-benchmarks

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/16dd6308e40000

📍 Found significant differences after each of 3 commits.
https://pinpoint-dot-chromeperf.appspot.com/job/16dd6308e40000

[Intl] Ship Intl.RelativeTimeFormat by ftang@chromium.org
https://chromium.googlesource.com/v8/v8/+/a3b97babfb19490a948a931b3966cf4ff8c2a2bd
memory:chrome:all_processes:reported_by_chrome:v8:effective_size: 3.327e+06 → 3.595e+06 (+2.68e+05)

[Intl] move DateTimeFormat.prototype.resolvedOptions to c++ by ftang@chromium.org
https://chromium.googlesource.com/v8/v8/+/d34ffa6a3822fb7ca73ea0b6f7c6f8a27ea0fd79
memory:chrome:all_processes:reported_by_chrome:v8:effective_size: 3.567e+06 → 3.595e+06 (+2.79e+04)

Revert "[interpreter] Separate bytecodes for one-shot property loads and stores" by mslekova@chromium.org
https://chromium.googlesource.com/v8/v8/+/3c3330f6f0cae9a4c894cbf030d742c25358a1db
memory:chrome:all_processes:reported_by_chrome:v8:effective_size: 3.595e+06 → 3.594e+06 (-1334)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  None

The memory regression was due to a CL reverted, which is now relanded as https://chromium.googlesource.com/v8/v8/+/1bff2e991e5a2d42dc6d24d85ffc70865ef5ab64

This should fix the regression once the CL is rolled into Chromium.