During past year of our development, our entire studio must restart unity several times per day (me personally like 10 times) because the RAM usage increases beyond 20 or 30GB.
The asset indexing is broken, where just opening prefabs keeps updating index. In the video bellow, you can see I started with 6GB, and went to 13GB by simply opening and saving prefabs, nothing else, in 3 minutes! Now image how a day full of work looks for us…
Here is a video with proof how broken it is, and its honestly a nightmare to work in unity for all of us.
After I finished video, several minutes later, unity was still triggering indexing out of nowhere, and RAM usage went to 27GB (with no input from me as user at all)
Creates 2 tickets for Unity already, one is now 3 months old, without change, and now another ticket explaining exact reproduction steps tracked to asset indexing breaking project and consuming all OS memory.
Sorry for the delay ins answering your question. We have investigated the bug and we have been able to repro it.
We have done a few fixes in the indexation to fix both the indexation time and the memory consumption. These fixes should be available in the latest 22.3 or 23.3 (unity6).
We are looking at changing the backend solution for asset indexing. This will be a more long term goal but it is paramount for us to solve the memory issue. Hopefully we will have news to share about this in the next few months.
In the meantime you can reduce memory consumption if you tweak your index options.
You can open the Index manager (Window → Search → Index Manager) and tweak your settings
If you think some folders shouldn’t be indexed, ad those to the Exclude list.
Ensure that you are not indexing subobjects
If you d not need property searching you can uncheck Properties.
Focusing on stability for memory improvements is a great investement for the engine, as its a much needed change, especially for large projects.
I have for now tweaked the indexing as you suggested, this made quite a difference, will distribute it to the rest of the team, so again, big thanks for this, it saves a lot of RAM just this single change
You said you have logged tickets about the memory trouble with indexing. Can you give me the links of those tickets? Did you attach a repro projects for those bugs?
Hi, yes the ticket is UUM-85044 and it has been confirmed and transfered to the dev team already.
I think I have uploaded the project, but I can no longer see the link there (as I think you guys rewrite the tickets for better wording and steps to repro)
I have the ticket and the project is attached to the bug. I will investigate this further. Like I said, during the past few months we have improved the memory space used durng indexation. But it seems your specific issue might be related to another thing we need to fix.