Search Issue Tracker
Won't Fix
Votes
0
Found in
5.4.0b6
Issue ID
771036
Regression
No
[Meshes][API] Out of memory crash when setting Mesh.subMeshCount to stupid high value
We don't want to add a maximum value for submesh count. If user put a crazy number, then he could get a memory allocation error.
Performance team said that they may add some custom flags on "dynamic_array" so the client code could test if a memory overflow appears or not, so when they'll add that feature to dynamic_array, client code should be changed according to that.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment