Crash on MemoryManager::OutOfMemoryError when performing various Unity operations

6.7.X

As Designed

Thank you for reporting a bug to Unity. After reviewing the behavior, we've confirmed it aligns with the current design and intended use of the feature. We understand this may differ from your expectations or workflow. We will close this case as 'As Designed.' If you have feedback on how the feature could better meet your needs, please let us know - we value your input and consider it in future improvements. After analysing the crash reports and Editor logs, this crash is the Editor running out of available system memory rather than a specific bug in a single feature. The reported call stack (in the Asset Database) is simply where the failure tends to surface, but the underlying cause is memory exhaustion on the machine, which is why it shows up across a wide range of different operations. A possible contributing factor is the number of parallel asset import workers the Editor runs. By default this is based on your CPU core count, and each worker is effectively a full Editor process that uses a significant amount of memory. On machines with a high core count but a more limited amount of RAM (for example, many laptops with 8 GB), the main Editor plus several import workers can exceed the memory the system has available, especially while importing many, large assets. As a workaround, you could try lowering the Desired Import Worker Count (Project Settings -> Editor -> AssetPipeline, or -desiredWorkerCount on the command line), and see if this eases the memory pressure.