Search Issue Tracker
Fixed in 2022.2.2f1
Fixed in 2022.2.X, 2023.1.X, 2023.1.0a22
Votes
0
Found in
2020.3.36f1
2021.3.6f1
2022.1.8f1
2022.2.0b1
2023.1.0a3
Issue ID
UUM-20502
Regression
No
Opening and closing the Shader Graph window causes a memory leak
Reproduction steps:
1. Open the attached project
2. Open Task Manager to monitor RAM consumption, note current RAM consumption
3. Open TestGraph from the Assets folder
4. Close the Shader Graph window
5. Repeat steps 3 and 4 ten times
6. Observe RAM consumption in Task Manager
Expected result: Memory consumption stays the same
Actual result: 300-500 MB added to memory consumption
Reproducible with: 10.9.0 (2020.3.36f1), 12.1.7 (2021.3.6f1), 13.1.8 (2022.1.8f1), 14.0.3 (2022.2.0b1), 15.0.0 (2023.1.0a3)
Reproduced on: Windows 10
Note: Each cycle of opening/closing the Shader Graph window consumes about 30-50 MB of RAM
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2023.1):
The shader graph window was not properly disposing of its view/visual element resources. Thank you for reporting this issue and bringing it to our attention. We now are disposing of the memory allocated by the view and this leads to fewer memory leaks. There is more work that can be done here to further reduce the amount of leaked memory and left over garbage, and this will be addressed in the future.
Resolution Note (fix version 2022.2):
fixed in 2022.2.2f1