Search Issue Tracker
By Design
Votes
2
Found in
2019.4
2020.2
2020.2.6f1
2021.1
2021.2
Issue ID
1317813
Regression
No
Assertion failed on expression: 'a.size == b.size' when rendering SkinnedMeshRenderer after attritube change
How to reproduce:
1. Open the user's attached "cam-skin-render-bug.zip" project
2. Open the "cam-skin-render-bug" Scene
3. Select the "script" GameObject in the Hierarchy window
4. Make sure "Bug" property is checked in the Inspector window
5. Enter Play Mode
6. Observe the Console log
Expected result: No errors are thrown in the Console log
Actual result: "Assertion failed on expression: 'a.size == b.size'" error is spammed in the Console log
Reproducible with: 2019.4.21f1, 2020.2.7f1, 2021.1.0b9, 2021.2.0a7
Could not test with: 2018.4.32f1 ('Texture2D' does not contain a definition for 'graphicsFormat)
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
- Crash on GizmoDrawingPhysics2D::DrawCompositeCollider2DGizmo when opening a Scene that has corrupted GameObjects with Tilemap Components
- Scrolling vertically and horizontally is very fast when in Play Mode and RuntimeInputBackend is set to UIToolkitInputBackendOption.Default
- Crash on MemoryProfiler::UnregisterAllocation when initializing entities and leaving Play Mode with Occlusion Culling enabled
- Crash on mdb_page_alloc when opening a project that was running while the PC shut down
- macOS Player freeze when using RunInBackground and Command+Tabbing to and from the application
Resolution Note:
This case has been closed by-design, however the problem area has had some changes. Now, instead of an assert being thrown a more helpful error message is generated and rendering of the Skinned Mesh Renderer is aborted. This is because the internal state of the skinned mesh renderer needs to track to mesh assigned to it, if that internal state isn't update then it can cause GPU crashes on Metal API based devices. After mesh swap the component must be given a chance to resync it's internal state to prevent this, this is done as part of the normal Unity update flow and happen after all user update method have run.