Search Issue Tracker
Won't Fix
Votes
6
Found in
2020.3.46f1
2021.3.20f1
2022.2.9f1
2023.1.0b6
2023.2.0a4
2023.3.0a3
Issue ID
UUM-29173
Regression
No
Unity doesn't free up memory when deselecting items which were used by Scripted Importers
Reproduction steps:
1. Open the attached project “MemoryRepro”
2. In the Project window select the “Assets/Resources/Smart Textures” folder
3. Duplicate the “Smart Texture” folder multiple times until there is about more than 254 of the same folder
4. Open “Activity Monitor” on macOS or “Task Manager” on Windows and inspect the memory usage of Unity
5. Deselect and select the same objects 6 times
6. Again inspect the memory usage of the Unity process
Expected result: Unity is using less than 2 GB of memory
Actual result: Unity memory usage is reaching about 30 GB or more
Reproducible with: 2020.3.46f1, 2021.3.9f1, 2021.3.20f1, 2022.2.9f1, 2023.1.0b6, 2023.2.0a4
Reproducible on: macOS 13.1 (Intel), Windows 10
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note:
We can't reproduce this issue.
Tested with 23.3, 23.2, 23.1, 22.3 and 21.3 using the provided test project.
Repro steps:
- Duplicate the Smart textures folder in resources multiple times (111!) while unity is closed.
- Open the project.
- Shift + select in the project browser Smart Textures folder and look at task manager to see that unity memory is increasing up to 30Gb.
- Unselect the folders. Wait a bit
- And see that Unity is back to ~3-4 GB.
So it seems the issue was fixed at an unknown time or we don't have accurate repro steps.
Feel free to reopen this ticket if you think this was not actually fixed and you have more precise steps.