Copyright © 2026 Unity Technologies
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.
fixed in 2022.2.2f1
Thank you for reporting this issue and bringing it to our attention. A fix for this issue will be landing on 2022.2
We're not able to backport the fix for this issue at this time. It introduced some unexpected behavior in more recent tech streams. We would like to avoid disrupting the now LTS experience for the 2021 version.
This issue shouldn't have been repro-ing this far back in 2020.X. Will definitely investigate if it is specifically reported that the issue persists in that version of the editor. The work done to improve the issue from 2023.X, 2022.X and 2021.X cannot be easily transferred to the state of the ShaderGraph tool as it was in 2020.3 as the code under the hood was very different.
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
Issues you vote on will appear here