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
- [Android][Sentis] Human poses are not detected when using the BlazePose model
- Sprite Editor Outline Tool Overlay is not displayed when no Sprite is selected
- “No method with RuntimeInitializeOnLoadMethod attribute” warning from ReadmeEditor.cs is thrown after installing Project Auditor Rules
- Projection matrix is altered when using RasterCommandBuffer.ClearRenderTarget on DX12 and Metal
- Entities Hierarchy window allows Cyclic nesting and throws an “ArgumentException: Cyclic nesting detected” error when dragging a Prefab onto the same Prefab in the Entities Hierarchy
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.