Search Issue Tracker
Won't Fix
Votes
1
Found in [Package]
4.10.0, 7.0.0
Issue ID
1172875
Regression
No
Changing VFX graph capacity to a high number results in Unity running slow, unrelated panels/windows artifacts, crash
How to reproduce:
1. Open attached project "VFXDisappear.zip" and scene "SampleScene" (a visual effect in the scene must be present)
2. In Hierarchy window, open "New VFX" Visual Effect
3. In Visual Effect window, change capacity to 9999999 and press enter (might need to change between 0 and 99999999 a few times)
4. Observe the Editor
Expected result: the Editor runs normally
Actual result: the Editor start to run slow, visually corrupting unrelated programs and crashing after some time
Reproducible with: 2018.4.5f1(4.10.0), 2019.1.13f1(5.16.1), 2019.2.0f1(6.9.1), 2019.3.0a11(7.0.0)
Could not test with: 2017.4 (HDRP was not yet implemented)
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:
we don't want to implement a hard limit (same with most areas in Unity, you can always stall/crash the editor if you push the hardware).
A visual cue will be provided with the upcoming error feedback to give users more info within the graph itself.