Search Issue Tracker
Third Party Issue
Votes
2
Found in
2021.3.33f1
2022.3.14f1
2023.2.1f1
2023.3.0a16
Issue ID
UUM-57060
Regression
No
Custom GameObject crashes the Editor when the Mesh Collider Component is added
How to reproduce:
- Open the “MeshColliderCrash bug.zip“ project
- Select the “crashing-mesh-collider“ GameObject in Hierarchy
- Add a Mesh Collider to the GameObject
- Observe the Editor
Expected result: The Mesh Collider Component is added
Actual result: The Mesh Collider Component causes a crash
Reproducible in: 2021.3.33f1, 2022.3.14f1, 2023.2.1f1, 2023.3.0a16
Reproduced on: Windows 11 Pro
Not reproduced on: Mac M1 12.6.1, Mac M1 13.5.2, Linux Ubuntu 20.03 5 LTS
Notes:
- Workaround: Before adding the Collider remove the Mesh from the Mesh Filter Component, Add the Mesh Collider, and Assign the “crashing-mesh-collider“ Mesh for the Mesh Filter and the Mesh Collider Components
- After the workaround Information, Warnings, and StackOverflow Errors appear in the Console, and memory usage is increased when anything is changed within the Editor (most noticible by toggling the Convex property off, see the workaround video)
- Bug reporter window does not open after the crash
WORKAROUND: Disable the fast midphase cooking option.
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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Resolution Note:
This is a problem in the PhysX version we're using at the moment. For until we have a newer version that doesn't suffer from this problem, a possible workaround is to disable the fast midphase option in the MeshCollider cooking options.