I've noticed that RAM usage increases over time when creating new worlds, and it often never goes back down. When taking screenshots with printscreen, it'll often be a picture of something several minutes old, potentially even a previously-loaded world. This can also happen when quitting out of a world, particularly as RAM usage approaches the total system memory.
Why does this happen? Is there anything that can be done about it? It's very odd behavior that I haven't been able to find any explanations for, maybe because I don't have any specific terms to search with. It's a source of frustration when attempting to generate a good map (or even just checking behavior of worldgen) with various combinations of mod or even just stock vanilla, as I have to quit out of VS entirely for it to finally let go of the RAM it's grabbing. As an example, upon launching VS, it holds steady at about 10-11GB of RAM use (counting Firefox, which I'm using to write this post of course.) RAM usage climbs to 17-18GB upon creating and loading into a world for the first time. If I quit out and then go create a new world, usage climbs further into the low 20's, and will eventually hit around 29GB of my 32GB of memory on a third repetition. Even if I leave the game idle on the menu for a few minutes between iterations, the RAM usage never drops back towards the original 10-11GB or even the 17-18GB used when only a single world is active.
Why is the game seemingly holding onto assets for worlds that aren't in use anymore? Shouldn't it discard all of that once the world has closed and been saved to disk?