Search Issue Tracker
Won't Fix
Votes
0
Found in
5.4.0b6
Issue ID
771038
Regression
No
Unity freezes and later crashes when setting uvAnimationTile on legacy ParticleRenderer to a high value
Add the following code to the Start method of any script attached to a gameobject in your current active scene and press Play. Unity crashes!
ParticleRenderer p = gameObject.AddComponent<ParticleRenderer>();
p.uvAnimationXTile = int.MaxValue;
p.uvAnimationYTile = int.MaxValue;
Calling this code froze Unity and my MacBookPro in a way where I couldn't even force quit out of it and the laptop got so hot I thought it would literally melt.
Maybe those two values should be capped to some sensible values.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Stage information is not logged when Log Shader Compilation is enabled
- [Vulkan] The memory allocation increases rapidly when there are multiple (three or more) Real-Time Reflection Probes in the Scene
- [macOS] Library folder of the opened project can be deleted which leads to the crash
- “Default Scene” dropdown field contains a spelling mistake “Default Builtin”
- Editor crashes on PPtr<Mesh> after adding Text Mesh and Cloth Components to the same GameObject
Add comment