Search Issue Tracker
Fixed in 14.0.2
Votes
1
Found in [Package]
12.0.0
Issue ID
1305929
Regression
Yes
[VFX] Empty Visual Effect Component generates about 14 KB of Garbage every frame in the Editor
1. Open the attached project named "Case_1305929"
2. Open the SampleScene
3. Open the Profiler Window and switch it to the Editor mode
4. Check the reading for GC allocations in the Memory section
5. Right-click in the Hierarchy window and add a new Visual Effect object
6. Observe the GC allocations again
Expected results: GC Alloc does not increase, or increases only marginally since a new VFX object is completely empty and does not have a VFX asset assigned
Actual results: GC Alloc increases by ~14KB OR by ~25KB if the Visual Effect object is currently selected in the Inspector window
Reproducible with: 7.5.2(2019.4.19f1), 2020.2.3f1(10.2.2), 2021.1.0b3(11.0.0), 2021.2.0a2(12.0.0)
Notes:
1. Reproducible with URP and HDRP
2. Does not reproduce in a Build
3. The memory amount does not seem to increase when the number of Visual Effect objects is increased. GC Allocated memory stays the same as described in the Actual results section
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
- [tvOS] Project crashes on startup on Apple TV simulator (both X86_64 and ARM64 architectures)
- Context menus open on a different monitor when there are three monitors used
- Crash on Umbra::QueryExt::queryStaticShadowCasters when opening a specific project
- Crash on GfxDeviceD3D12Base::DrawBuffersCommon when opening a specific project
- Shader variants are recompiled while Building when the Platform is switched and changed back after the first Build
Resolution Note (fix version 14.0.2):
Fixed in 2022.2.0a9 with VFX package version 14.0.2. GC allocations have been reduced. While Visual Effect object is selected - ~13.7KB (Versus ~25KB in previous versions). While Visual Effect object is not selected - ~7.5KB (Versus 14KB in previous versions)