Strings generated by outerHTML not accounting for size in GC
This page calls outerHTML in a row from a high-frequency timer.
This generates strings owned by GC'ed objects, without accounting for the size of the string.
You can observe how the memory grows via Chrome's Task Manager.