Question Strange Memory leak on 2022.3.x

Hi all,

So this is an odd one. My game when run on 2021.3, memory sits around 1.3GB on launch. However, ive had reports since making changes over the last couple of months that some users are seeing around 10GB.

I got one user to do a memory capture with the Unity 2022.3.4f1 memory profiler, and it shows memory usage at around 1.6GB, however his task manager claims it is using 10GB.

Im guessing that this is because the leak is outside of my code. Is there anyway to track this leak?
My external DLLs that I use are Steam Audio (already tried downgrading this), Steamworks SDK 1.57 (already tried downgrading this too).

He also ran it once and it didnt leak memory.
Just not quite sure how to deal with this, I guess I could try downgrading to 2021.3 again, but that would mean rewriting my navmesh stuff and a few other bits, which isnt ideal.

 

0 changes to code
Changed version to 2021.3.28f1
Recompiled
Memory leak gone.
Guess that settles what version im sticking on for a while!

 

when i have two game windows the game ram goes crazy, like unity starts growing from 1gb to 5 gb to 10 to then 16 to then crashing my system lol, cant have two game windows at the same time

 

I found “the” memory leak on 2022.3.x. I don’t know if its the same one as the OP but its been around since 2022.1 beta and I am surprised nobody has noticed it.

I posted about it here: https://forum.unity.com/threads/2022-3-9-uielements-memory-leak.1491019/

Is it possible to launch a production ready game with this type of memory leak? I never have had to experience this before but it seems extremely bad. It makes safari on webgl crash quickly.

 

Dang . That is good and bad news then. I hope the OP figures out their issue but at least its one less leak they surely have. Thanks!

 

I am having the exact same problem. When I Drag out the Scene view or the Game view or any view actually, thus having "2 windows", or even when I splitscreen the scene and game view in the same window. The RAM bumps up rapidly and crashes my computer.

I am fairly sure this happened after updating from 2021.3.25f1 to 2022.3.8f1

edit: I've just read that something got fixed in 2022.3.10. I'll try that out right away.

edit2: Yep that fixed it.

 

@TwoYen were you getting the same issue I have mentioned on this thread, please let me know. I have been stuck on this since weeks and do not know how to fix this. Please confirm that mine issue is same as yours and which got fixed by upgrading Unity to 2022.3.10f1.
Thanks

 

I am having a memory leak issue on 2022.3.16f1

 

We are having a memory leak issue on the Windows il2cpp build of 2022.3.20f1, too!

We use the following repositories with Google MediaPipe for our development:
https://github.com/homuler/MediaPipeUnityPlugin

The attached images are the results of a Windows il2cpp build of this project on 2022.3.20f1 and 2021.3.28f1, observed in the profiler after about 12 hours! In 2022.3.20f1, "Total Used Memory" increases to 1.5GB and "GC Used Memory" to 1.32GB. (In 2021.3.28f1, it does not increase much.)

I analyzed using Memory Profiler on 2022.3.20f1, and the "Managed Reserved" is only increasing, as shown in the other attached image.

The MediaPipeUnityPlugin performs GC Allocation in a thread that is not the main thread, so that may have something to do with it.

Do you know what it is?

 

I tried to stop updating that plugin thread and the strange memory leak stopped. Indeed, it seems likely that the native plugin was holding memory.
However, it is true that this event does not occur in 2021.3.35f. Was there some update between 2021.3 and 2022.3 that dealt with native plugins?

 

I also built this plugin on a Mono build to test it out. As a result, I have discovered that this does not occur in the Mono build, but in the Windows il2cpp build. So I suspect that this is not a bug caused by the plugin, but by using the native plugin with the Windows il2cpp build.

 

OK! I'll try to file a bug report. Thank you!