Steps to reproduce:

Load a save game and run it briefly. Load the same (or different) save over again without exiting the game. Repeat a few times and watch the memory usage increase, often several gigabytes each time. Exit the game and all the memory gets freed finally.

Use Cases:

1. As a new player, I sometimes try things and restart from the same save repeatedly. For example when figuring out what works regarding retaining walls.

2. Or I swap between a sandbox save and my actual game to develop blueprints more efficiently as I build a blueprint library.

   Caveats:

I am running on Linux under Proton, so the increased memory usage eventually triggered the OOM killer and made me investigate. However, I am guessing the memory usage also increases under Windows with the same repeated loading.

We are aware of this problem and we are working on it, the problem is fragmentation of the reserved memory pool, not a leak of resources.

Great, I'm glad to hear you are aware of the issue. It's easy enough to work around by restarting the game entirely after a handful of game loads. I've also seen other unity games struggle with similar memory issues in the past, so hopefully it can be resolved here as well.

Thanks for the great game!