The system is running out of memory. Please close applications to free memory or free up space on th

After a couple of times running the app in Oculus Link (especially!) from the Editor 2020.2 I get this memory message which requires to restart Unity:
The system is running out of memory. Please close applications to free memory or free up space on the partition where the pagefile is located.
Used memory (physical and paged): 94% (30828MB of 32724MB).
Discarding profiler frames data.

If I run the app without Oculus Link, I also get this error but after many runs.

I disabled the Virtual Memory from Windows.

Any ideas why this happens?

1 Like

#1) The profiler is a massive memory hog.
#2) This is a feature not a bug.

Clear the profiler history when you’re done with it, otherwise it’s basically a active memory leak. (It’s so you can dump it to disk for analysis later if you need to comb through the mass of data, or do stats analysis on it.)

In particular click “Clean On Play” in the top of profiler widow to clear it automatically.

No, that did not do it - issue still appears.

I can confirm that using both “clear” and “clear on play” does not solve this issue.

1 Like

Have you perhaps considered closing browser tabs/shutting down other programs? it sounds to me like it’s less of a unity problem and more of a “you have too much stuff open” problem.

Only application running was Unity in my case. Pretty frequent issue whenever the Profiler is running, and never happens when it’s not.

The unity editor is a memory hog. Better not disable virtual memory…

1 Like

Dude just give screen shots of your task manager next time this is a problem, or better yet do a memory capture using the unity memory profiler, or the normal profiler, to figure out what your memory hog (or leak) is on your own – and then ask for detailed advice about how to fix it.

Vague “memory overused” isn’t giving us much of anything to work with.

I’m facing the same problem (Unity 2020.3.0f1). Profiler does not work at all! Error:
The system is running out of memory. Please close applications to free memory or free up space on the partition where the pagefile is located.
Used memory (physical and paged): 40% (5735MB of 14336MB).

1 Like

Randomly started happening to me as well after starting the profiler. Started happening to my teammate a few days later without him using the profiler. Even more strangely, we haven’t merged our code yet so it can’t be a new feature we added, simply a coincidence.

The only other thing I have to add is we’re both on M1 macs, Unity 2019. I updated the Unity Hub Beta 3.0.0-7 but he didn’t…

Edit: Seems to be happening to other people randomly as well: Unity says: "The System is Running out of memory." when it is not. - Questions & Answers - Unity Discussions

Hello Y’all,
For Mac M1 chips we are now tracking this as a bug, case 1386242.

6 Likes

Is there any temporary workaround?
I’m afraid that the fixes will come at the farthest on 2021.2.x and currently can’t risk going above 2021.1.28f1.

Tried lowering the Frame Count of the profiler but it doesn’t allow less than 300.

Non that I know of. 2021.1 is a tech release version that is no longer receiving updates so you should really not stay on that one. You will eventually have to update to 2021.2/3 and maybe stay on 2021.3 (the 2021 Long Term Support version) if you need to reduce your upgrade risk while maintaining access to fixes.

That is unless you’re not on 2021.1 yet but 2020.3. there is a backport planned for 2020.3

1 Like

Hi, I’m using 2021.2.11f1 and I cannot use the profiler due to lack of memory:

The system is running out of memory. Please close applications to free memory or free up space on the partition where the pagefile is located.
Used memory (physical and paged): 48% (5416MB of 11264MB).

I’m using a Macbook Air M1 2021.

The backport for the fix of case 1386242 has landed on 2021.2 and will become available with 2021.2.13f1.

1 Like

I’m seeing this out-of-memory error on an M1 Mac Mini with deep profiling disabled. Is this a separate bug, or should I consider it the same?

[Edit] I should also specify that this is while I’m profiling in-editor, in Play mode, rather than profiling a standalone process.

It’s pretty likely to be the same and since the backports for the fix are ongoing, it’s probably best to wait for those to land on an Editor Patch Release within the mayor version stream you’re on and try to reproduce it in that version with the fix.

1 Like

Yeah, I’m currently on U2021.2.9, I’ll keep an eye out for .13

1 Like

Just to follow up: it looks like U2021.2.13 was released; and indeed, I can correctly connect to and profile on running devices.

1 Like

I use 2019.4.28f1 and am getting the same error for both normal and deep profile.