Search Issue Tracker
Duplicate
Votes
0
Found in
5.5.2f1
Issue ID
891565
Regression
Yes
Unity crashes in <physx::Sc::Scene::release>, because the mesh bounds do not change after the mesh is set to Plane
Reproduction steps:
1. Create the new project;
2. Create Empty GameObject and add Cloth component;
3. Change Mesh to Plane and turn off Select Mesh window;
4. Change Mesh to Cube, turn off Select Mesh window and enter Play mode;
Actual result: Unity crashes in <physx::Sc::Scene::release> (actual_result.gif).
Expected result: Unity should not crash (expected_result.gif).
Note: if the scene is saved with the object which mesh is set to Plane and you open the project and change mesh to Cube, Unity not always crashes. However, Unity always crashes, if you repeat reproduction steps (when the project is new). The crash is caused because the bounds do not change after the Plane mesh.
Reproduced with: 5.5.0a1, 5.5.2p3, 5.6.0f1, 2017.1.a04
Not reproducible with: 5.3.7p4, 5.4.5f1
Regression introduced in 5.5.0a1
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
- Spring Joint shows only one anchor gizmo in Scene view when "Auto Configure Connected Anchor" is enabled
- Crash on _platform_memmove after entering large value in Graphics settings Preloaded Shaders field
- Disproportionally large impact on CPU frame time when writing to a rendering entity's LocalToWorld
- "Constant Force" Component numeric fields drift out of view while entering a really big value in the Inspector
- Scene view camera speed pop-up appears empty or cut off when Scene view is very narrow
This is a duplicate of issue #845868