Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.4.X, 2018.1.X
Votes
0
Found in
2017.2.0f3
Issue ID
976095
Regression
No
Crash on Rigidbody::CleanupInternal on disabling GameObject with Rigidbody and Wheel Collider components
The crash appears only if both parent and child GameObjects have a Wheel Collider component and the parent GameObject has a Rigidbody component which is positioned before Wheel Collider component in the Inspector window.
Reproduction steps:
1. Open Unity editor and create a new project
2. In the Hierarchy window create an empty GameObject (will be called parent GameObject for clarity)
3. Add Rigidbody component to the parent GameObject
4. Add Wheel Collider component to the parent GameObject
5. In the Hierarchy create an empty GameObject as a child to the parent GameObject
6. Add Wheel Collider component to the child GameObject
7. Save the scene
8. In the Inspector window disable parent GameObject
Actual result: Editor crashes
Expected result: Parent GameObject is disabled
Reproducible with: 5.5.5p2, 5.6.4p4, 2017.1.2p4, 2017.2.1f1, 2017.3.0f2, 2018.1.0a7
Notes:
As a workaround in the Inspector window move parent Gameobject's Wheel Collider above its Rigidbody component
Fixed in: 2018.2.0a8
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Default Preset application and Reset() method execution order is different when adding a Component via the Inspector versus calling Reset via the Component context menu
- Scene view is not outputting HDR when the "Use HDR Display Output" option is enabled, DX12 is selected as the Graphics API, and URP/HDRP is in use
- Sprite Atlas results in suboptimal packing even when "Allow Rotation" is enabled
- References placed in a UnityEvent change to the same reference when multi-selecting their GameObjects
- "ShadowCaster2D" Component doesn't work when the "Casting Source" is set to "Polygon Collider 2D"
Add comment