Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.2.X
Votes
1
Found in
2019.4
2019.4.4f1
2020.2
Issue ID
1267820
Regression
No
Editor crashes on CompressedMesh::Compress when using VertexAttributeFormat.Float16 and Mesh compression is enabled
Reproduction steps:
1. Open the attached "MeshCompressionCrash.zip" project
2. Right-click on the "face.fbx" in the Project window to open the context menu
3. Select Reimport
-- Observe the crash
Reproducible with: 2019.4.7f1, 2020.1.1f1, 2020.2.0a20
Could not test with 2018.4 due to multiple compilation errors
Note: two asserts are failing before the crash occurs:
1) Assertion failed on expression: 'chantype.format == kVertexFormatFloat'
(Filename: C:\buildslave\unity\build\Runtime/Graphics/Mesh/CompressedMesh.cpp Line: 370)
2) Assertion failed on expression: 'chanType.dimension == 0'
(Filename: C:\buildslave\unity\build\Runtime/Graphics/Mesh/Mesh.h Line: 140)
Top 5 lines of the stack trace:
0x00007FF785E11660 (Unity) CompressedMesh::Compress
0x00007FF785DC476D (Unity) Mesh::Transfer<StreamedBinaryWrite>
0x00007FF784C3922B (Unity) SerializedFile::WriteObject
0x00007FF784C034C9 (Unity) PersistentManager::WriteFile
0x00007FF784C04374 (Unity) PersistentManager::WriteFile
<...>
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2020.2):
Fixed in: 2020.2.2f1
Resolution Note (fix version 2019.4):
Fixed in: 2019.4.16f1