Managed Heap memory leak

Diving into my profiler, it's evident that ManagedHeap.UsedSize is continuing to expand as I run my game.

I don't think I'm doing anything egregiously bad during gameplay. However, since my game is procedurally generated, a lot of things need to get instantiated at the beginning of a level.

Here's the thing: My game doesn't require that the Unity scene be switched in order to change levels, since it's all procedurally generated. However, if I DO switch scenes between levels, this seems to prevent the memory from getting too high -- or at least alleviates the issue to a good degree. The downside to this is, in this particular case, that switching scenes causes my game to suffer slower load times.

I'm not sure how much there is I can do with my code to prevent ManagedHeap.UsedSize from climbing. I've attempted pooling a lot of the things I was instantiating, but this only alleviates the issue rather than completely solving it.
Having followed the guidelines on the this page, I'm not sure where to go from here.

Is there no way to just reduce the managed heap? Meaning, achieve something similar to a scene change, without actually changing the scene?

 

It's difficult to diagnose memory issues without knowing all the gritty details of how you've implemented your systems. However, if reloading the scene fixes the problem, then you're probably not doing something that is allowing all of your old objects to be completely unloaded from memory. Do you use many non-MonoBehaviour classes?

 

I'm using non-monobehavior classes here and there, though some of them may be attached to a large number of objects. Is this something that should be avoided? Is there an ideal way to unload these from memory?

Also - Upon further inspection, reloading the scene doesn't necessarily "fix" the problem as well as I'd like. There have been points where reloading the scene actually resulted in increased memory usage, though this wasn't common.

 

Are you profiling the editor, or a built game?

 

I've profiled both, the same rise in memory usage occurs in either case.

 

Off the top of my head, I'm afraid I can't give you more specific advice other than to make sure you have a good handle on the lifecycle of all of the objects you're creating. It's possible that somewhere in your code you are accidentally keeping something in memory and making GC unable to collect it. It's also worth seeing if

Resources.UnloadUnusedAssets

does you any good.

 

Have you tried Unity's memory profiler already?
https://bitbucket.org/Unity-Technologies/memoryprofiler

If your game is leaking memory, you should be able to see a specific object type grow in this tool. Otherwise it could be memory fragmentation.

 

@Peter77 I have a similar issue as Doghelmer is facing. But in my case memory rise happens only in the application and not in the editor.

 

You can also use Unity's Memory Profiler to analyze memory of a build. The tool works for both, builds and editor.

Unity's new Memory Profiler
https://forum.unity.com/threads/new...e-for-unity-2018-3-and-newer-versions.597271/