Landscape Memory Bug (Leak?)
I've noticed a problem when moving my project from 4.13.2 to 4.14.1 that there's a memory bug associated with the landscapes where if I reload any level with a large landscape (not sure which size it starts occurring but going with the biggest size which I currently want has an issue: 255x255, 2x2, 16x16, 8161x8161, 256) or a different level and go back to the same one with the landscape, the memory is never freed and any memory associated with the landscape is added back on top, ranging from 50 to 300 MB every reload. I tried this with both level streaming and open level commands and was able to reproduce this on a new project as well.
So I ran some more tests and actually encountered a blocker when trying to test the memory leak. I will say the tests I ran (reloaded the level 10+ times) were not producing a memory leak on my end. I did experience a crash however, which I have logged a ticket.
The crash I logged could very well be related to the memory leak/issue you are reporting, but it will be hard to tell until it gets fixed and you run additional tests. For tracking purposes you can see the issue I logged by following the link below.
Let me know if you have additional questions or comments.
answered Jan 05 '17 at 10:32 PM
Follow this question
Once you sign in you will be able to subscribe for any updates here