Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2020.1.X, 2020.2.X
Votes
0
Found in
2019.4
2020.1
2020.2
2020.2.0b8
2021.1
Issue ID
1288561
Regression
No
Crash when optimizing Mesh which contains overlapped indices in sub meshes
Reproduction steps:
1. Open attached project ("MeshOptimizeCrash-2020.2.zip")
2. Click on the "Run" menu option (Test/Run)
Expected result: Editor does not crash
Actual result: Editor crashes with stack trace:
0x00007FF65254A593 (Unity) Mesh::SetIndexData
0x00007FF65254AA23 (Unity) Mesh::SetIndicesComplex
0x00007FF65256F8E3 (Unity) OptimizeTypedIndexBuffers<unsigned int>
0x00007FF65254451E (Unity) Mesh::Optimize
0x00007FF652DFADA2 (Unity) Mesh_CUSTOM_OptimizeImpl
...
Reproducible with: 2019.3.0b1, 2019.4.14f1, 2020.1.13f1, 2020.2.0b11, 2021.1.0a5
Could not test with:2019.3.0a12 and earlier versions due to multiple compilation errors (e.g. "The type or namespace name 'SubMeshDescriptor' does not exist in the namespace 'UnityEngine.Rendering'")
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crashes when loading RenderDoc with Graphics API set to OpenGLES2 or OpenGLES3
- [Windows] Development Build with no scenes shows a purple screen when using OpenGLES3 graphics API
- Shader variants take too much memory at runtime
- [HDRP][VFX] Output mesh with default shader is incorrectly sorted before the HDRP fog
- Error "'GamepadSpeakerOutputType' does not exist in the namespace 'UnityEngine'" occurs in the Console when building a project
Resolution Note (fix version 2021.1):
Fixed with 2021.1.0a8, backported 2020.2.1f1, 2020.1.16f1