Is anyone else getting massive memory leaks in Unity 2017.1.0f3? How I managed to do it was by leaving Unity open for about 4-5 hours and when I opened process hacker to see what was lagging my system, it said Unity.exe was using ~20GB of Memory (~6GB of RAM and ~14GB of Commit Charge). Anyone else experienced this? It’s mainly a bear bone project that I open in my case.
3 Likes
Yes I was having a similar issue detailed here:
I switched to a PC and so far have not had any memory problems.
I’m on Windows and experiencing this problem. It seems to be a mesh issue. I don’t know why but meshes keep piling up and up even though none change.
Yeah. It is happening since 2017.1 upgrade. My new highscore of Unity’s ram usage is 24 GB. 
1 Like
Oh damn, that beats my new record of 22GB. Unity really needs to figure out what’s going on and fix it. Otherwise people may start to downgrade to Unity 5 or just switch away from them.
1 Like
At this point I’m pretty confident this is a unity issue - whether it is related to macs, PC’s, unity 2017, unity 5.6, etc. is still unclear. It would be great to get some input from a unity mod. If things are as they appear, this is a very serious bug, making their product virtually unusable under some very easy to satisfy conditions. There is still the possibility that all of us are making the same stupid mistake, but it is getting less and less likely.
Anybody representing unity want to chime in here?
There’s a lot of forum threads. If you want a bug fix, file a bug report!
Did anyone file a bug report? Or did everyone post on a forum and hope that somebody saw the post?
I filed a report. I’m currently talking to a QA guy, but he can’t reproduce the issue.
Let us know which issue is that, so we can check the patches when this issue gets resolved.
Thanks
I’m also occur this problem, I dunno.
Unity almost filling up my RAM up to 1 GB.
I’m also got an OOM error from both Windows and Unity.
Yes, I ran into this immediately upon porting my project from 5.x to 2017.1.0f3. It appears to be an internal leak coming from the UI system as I’m able to circumvent the issue for the time being by simply disabling it. Otherwise the editor will (eventually) crash with memory write errors.
Come on Unity - Some of us have better things todo than to chase internal memory leaks 
Did you file a bug report?
Do you have the latest graphics drivers? I had a memory leak after upgrading and it was resolved by upgrading my graphics drivers.
This had been reported way back during beta: https://issuetracker.unity3d.com/issues/possible-memory-leak-for-development-mode-standalone
It was flagged and discussed here: https://forum.unity3d.com/threads/2017-2-case-939424-shared-ui-mesh-memory-leak.486912/
And possibly here too: http://answers.unity3d.com/questions/1387757/unity-editor-memory-leak-1.html
Unity are well aware and hopefully working on a stable fix.
I hope they are, I cannot downgrade the projects I already upgraded AND I’m tired of 25GB of Private Data being used. Unity has even caused Windows to BOSD when I went to open the start menu. If they need an example project, I can hand them one. This one project I have causes ~0.15GB of memory to be leaked at once per second.
1 Like
Is this still occurring for you guys too in 2017.3.1? Also - how do you set the maximum RAM usage? It seems that Unity forces a crash at 1GB of ram usage even on systems with 32GB RAM etc