Immensely higher RAM usage than previous releases

[ArrayBolt3]

In the past (using Friction 1.0.0-rc1), I was able to easily handle projects with many thousands of frames (lyric videos) on a system with 32 GB RAM. Friction used a lot of memory, but it seemed to max out after a bit, usually consuming probably around 12-16 GB, which worked well.

Things seem to have changed in 1.0.0-rc3. Memory usage now grows at a rate of about a gigabyte per second while rendering a section of a video to preview my changes, and that memory does not seem to be released (at least not much of it) when the cached render becomes invalidated. If I start Friction, open a lyric video project, click the "Play Preview from Start" button, and let it run to completion on a 1920x1080 resolution video that is 1231 frames long so far, Friction's memory usage indicator states it's consuming about 21.5 GB. The project is ultimately going to be a bit over 6,000 frames long, so at this rate I'd need a system with probably well over 129 GB of RAM to manage it. Furthermore, when closing Friction, the window disappears, but the application continues running (and therefore consuming memory) until I manually kill it using htop.

Did something change recently with how memory is managed? Is there maybe a memory leak?

[ArrayBolt3]

I may have found the solution; there's a RAM limit setting in Preferences. It was originally uncapped, I set it to 16384 megabytes and it seems to be obeying that quite nicely. Dunno what the performance or functionality implications ultimately are, I'll probably set it to something a bit higher than that in the end.