Search Issue Tracker
Won't Fix
Votes
0
Found in
2020.3.35f1
2021.3.6f1
2022.1.9f1
2022.2.0a18
2023.1.0a4
Issue ID
UUM-11328
Regression
No
Memory usage is not decreasing after closing VFX graphs
Reproduction steps:
1. Open the attached ‘Test’ project
2. Go to the ‘Window → Analysis → Profiler’ and observe the amount of used memory in the Edit Mode
3. Open the ‘Assets/VFX Graphs/VFX_1’ and ‘Assets/VFX Graphs/VFX_2'
4. Note that memory usage has increased
5. Close both ‘Assets/VFX Graphs/VFX_1’ and ‘Assets/VFX Graphs/VFX_2'
Expected result: Memory usage decreases
Actual result: Memory usage remains the same
Reproducible with: 2020.3.35f1, 2021.3.6f1, 2022.1.9f1, 2022.2.0a18, 2023.1.0a4
Reproduced on: MacOS 11.6 (Intel)
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Resolution Note:
From Kah Yong Seow
"Please close this ticket as the cause of the slowness has been identified to be coming from a user script."
There is no clear evidence of a memory leak anyway. Memory is not necessarily reclaimed right away in the editor.