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

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


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

mac-10_13_laptop_high_end-perf

blink_perf.canvas - Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks

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

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

Record GPU memory usage for OffscreenCanvas/ImageBitmap on V8 by fserb@chromium.org
https://chromium.googlesource.com/chromium/src/+/754c97a74b5f84f5d7291c330dc23681cf600cfe
transferFromImageBitmap: 2.244e+05 → 2.624e+04 (-1.982e+05)

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

Benchmark documentation link:
  https://bit.ly/blink-perf-benchmarks

Issue 900333 has been merged into this issue.

This changes increases the amount of GC we do. Before ImageBitmap objects were not being cleared at all (leading to bugs that looked like memory leaks).

This is WAI.