Search Issue Tracker
Duplicate
Votes
1
Found in
2017.3.0b1
2017.3.0f3
Issue ID
991649
Regression
Yes
[WSA] The application throws Assertion failed on expression: 'mesh.HasChannel(comp)' when deploying under x86 architecture
Steps to reproduce:
1. Open the attached project
2. Open the Main.unity scene
3. Switch platform to Windows Store
4. Build
5. Open the VS solution
6. Deploy on local machine x86
Actual results: Application crashes
Expected results: Application should not crash
Note:
Assertion failed on expression: 'mesh.HasChannel(comp)'
(Filename: C:\buildslave\unity\build\Runtime/Graphics/Mesh/MeshScriptBindings.cpp Line: 36)
Reproduced with: 2017.3.1f1, 2018.1.0b7, 2018.2.0a1
Not reproduced with: 2017.1.3p1, 2017.2.1p4
-
dwhit
Jul 20, 2018 14:46
This bug is not a duplicate, and is still unresolved for me.
-
Micha_Sattler
Feb 16, 2018 13:26
Crash occurs when trying to access (read) the vertices of a Mesh that has just been created and added to a MeshFilter. Knowing this, the crash can be circumvented, but the app still shouldn't crash in this situation..
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
This is a duplicate of issue #981757