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

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


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

chromium-rel-mac11-pro
chromium-rel-win10
chromium-rel-win7-gpu-nvidia

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/13f21792240000

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

[oilpan] Cleanup tracing scopes by mlippautz@chromium.org
https://chromium.googlesource.com/chromium/src/+/c6ff060cc760c7cb8a44be7314ce5e96757213c6

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

Funky :)

Effective size flakes between two value, so I would ignore it.

v8-gc-full-mark-compactor_sum recovered after we fixed an issue where the trace events were not properly closed. This resulted in over-accouting GC times in V8.

 Issue 846681  has been merged into this issue.