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
- [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