Tacklecast has a severe memory leak

[Aida-Enna]

I left tacklecast up with no input (so it was showing the Genki logo with the "connect a console" or w/e) for a few days (I'm unsure of the exact time), and the memory usage skyrocked over time to 58GB of my 64GB of RAM (and 15% GPU, despite not doing anything).

I'd guess from this that the tacklecast has a pretty severe memory leak. I endtasked it immediately, but I'll leave it up again and provide more information when it does it again.

[CobaltDelta]

Dug into this a bit, though I'm mainly relying on a lot of Claude investigation and explanation. There was an unbounded sender/receiver pair used to move frame capture data into the renderer, and that might have been the culprit - since it always takes the latest frame, it's possible that any skipped frames would accumulate indefinitely. There's a PR out to replace it with a simple triple-buffer, and a pre-release based on it in the fork I made if you want to see if the issue still reproduces with the fixed buffer sizes.