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

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


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

android-nexus5x-perf
linux-perf
mac-10_13_laptop_high_end-perf

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

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

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/1744cdf2e40000

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1744cdf2e40000

Roll src/third_party/catapult e3b37a4725a0..1b6e81b579f3 (1 commits) by chromium-autoroll@skia-public.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/08b8a680b62a8d79006145c1d6e739fd7f7f3a64
memory:chrome:all_processes:reported_by_chrome:v8:allocated_objects_size: 1.411e+07 → 1.492e+07 (+8.04e+05)

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

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

The only CL in the roll is 
  1b6e81b579f317a1c69d06538f6c8ee48d062c5f
  "Overwrite the 'Content-Security-Policy' header in WPR replay."