Search Issue Tracker
Won't Fix
Votes
0
Found in
2023.1.0a4
2023.2.0a1
Issue ID
UUM-11072
Regression
No
Project consumes a lot of RAM when a lot of assets are in the project
Reproduction steps:
1. Open the user attached project
2. Open the "nothing" scene
3. Open Task Manager and observe RAM usage
Expected result: Editor consumes under 1.5 GB of RAM
Actual result: Editor consumes 7-8 GB of RAM
Reproducible with: 2020.3.37f1, 2021.3.8f1, 2022.1.12f1, 2022.2.0b3, 2023.1.0a4
Reproduced on: Windows 10
Note: memory consumption could differ depending on the version, also sometimes RAM consumption could spike up to 10-12 GB. Tested project is 50 GB in size. Possible memory leak
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Resolution Note:
We also see high memory use in the Editor here.
However, we have not seen any obvious memory leaks. The project is large and many of the items in it do use a lot of memory.
I'm closing this bug because we don't want to track this as a bug; there isn't a specific thing we can fix to reduce memory use here. Instead, we're moving this to the Optimization Team's planning tasks, and will look at making larger changes to reduce the Editor's memory use.