Browser Support • Re: Memory leak (?) on some PeerTube instances

Far as I can tell it's some shenanigans with recursive JS timeouts and callbacks, as there aren't specific callstacks and all the memory gets pooled into GC roots (and it'll happily keep gobbling up more and more memory in GC things - I let it run up to > 16 GB). The browser can possibly recover from it with full GCs and compacting after tab closure but it'll be (very) slow at least because it'll have to trace tens of millions of function instances. It may also give up if that takes too long.