Search Issue Tracker

Fixed in 2022.2.X

Fixed in 2020.3.X, 2021.2.X, 2022.1.X

Votes

12

Found in

2020.1.0b14

2020.3

2021.2

2021.2.5f1

2022.1

Issue ID

1386242

Regression

Yes

[M1] "System is running out of memory" error is thrown when using Profiler as a Standalone Process with Deep Profile turned on

MacOS

-

How to reproduce:
1. Open the user attached "URP_BasicDecalExample.zip" project
2. Enter Play mode
3. Open the Profiler as a Standalone Process (Window -> Analysis -> Profiler(Standalone Process))
4. Turn on the Deep Profile setting in the Profiler
5. Open the Console

Expected result: No errors
Actual result: A "System is running out of memory" warning and error is thrown

Reproducible with: 2020.1.0b14, 2020.3.25f1, 2021.2.7f1, 2022.1.0b2
Not reproducible: 2019.4.34f1, 2020.1.0b13

Note:
- Reproduction is somewhat inconsistent, multiple tries might be required
- Only reproducible on M1
- The issue is also reproducible when baking the scene
- The reproduction consistency is dependent on RAM

  1. Resolution Note (fix version 2022.2):

    Fixed in: 2022.2.0a5

  2. Resolution Note (fix version 2022.1):

    Fixed in: 2022.1.0b8

  3. Resolution Note (fix version 2021.2):

    Fixed in: 2021.2.13f1

  4. Resolution Note (fix version 2020.3):

    Fixed in: 2020.3.31f1

Log in to vote on this issue

Comments (13)

  1. hieutran196

    Apr 14, 2022 03:15

    I close profiler tab and issue was gone

  3. alexandre-fiset

    Mar 02, 2022 17:17

    This is marked as fixed in 2021.2.13f1 but is still happening when building our game and sometimes while importing. Just on Mac M1.

  4. QuestionsBrown

    Feb 21, 2022 13:56

    I have encountered the same issue on version 2020.3.26f1. I’m using URP inside an AR app on my 8GB 2017 IMac with no other applications running so I doubt I am truly running out of memory. Do you guys have any timetable for this 2020.3.26f1 fix?

  5. Alejandro-Martinez-Chacin

    Feb 01, 2022 15:32

    Excuse me for yet another message related to this, but it might be useful.
    It might really be that the system is running out of memory or at least it is being detected as such even if the Unity's reported log says 10% or 20% usage only.

    I have found, on my side, another machine, M1 Pro 16GB of RAM, that the profiler seems to work if I close most utility apps(*) that are usually opened
    It seems like if on Activity Monitor the memory pressure is on yellow, then the profiler will discard the frames, if it shows green it will work.

    This way I have had the profiler work on both 2021.1.28f1, 2021.2.9f1

    ---
    (*) Utility apps usually are: Teams, Discord, Slack, Outlook (web based), Figma, Notion, etc. The chatting apps themselves can gather up to 2-3GB of RAM (yeah, I know, full blown games need less than that), Outlook on it's own another 1 or 2GB depending on some context that I can't pin point, etc for a whopping 6GB not counting the rest of the system.

  6. Alejandro-Martinez-Chacin

    Jan 31, 2022 22:18

    Would be very curious to know if this is being worked on or backported from potential future versions that already work (if any)?
    Just tried the latest version to date, 2021.2.9f1 that came out what seems this week and the issue still persists.

    Would be also good to know if it is actually a reliable message (memory system is filled for profiling) or it is a bug since it says things like only 15% is in use yet there's not enough for profiling.

    If anyone with a 32GB system could chime in would be greatly appreciated.

    Thanks a lot in advance.

  7. manurocker95

    Jan 14, 2022 19:23

    This same error happens when baking lighting in big scenes with GPU

  8. Orkun_SRZ

    Jan 13, 2022 22:38

    Please fix.

  9. andrewpey

    Jan 11, 2022 04:01

    Yeah, it's 2020.3.x of course, thanks for the notice.

  10. Alejandro-Martinez-Chacin

    Jan 10, 2022 20:55

    To further expand, on a higher spec'ed system. Same behavior, just a lower "% usage% reported (less than 20%).
    MacBook Air 16GB, 1TB SSD (just 100GB used).

    On Unity 2021.1.28f1 and 2021.2.7f1 (Apple Silicon version) the error triggers.

    Regarding the original commenter, 2021.3.X, is that a typo relating to 2020.3.x instead?

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.

Latest issues

See all new issues