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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
Add comment