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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment