Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2020.3.X
Votes
0
Found in
2020.1.0b8
2020.2.0a8
2020.2.0a21
Issue ID
1272468
Regression
No
Crash on ArticulationBody::HierarchicalDestruction when entering Play Mode with Articulation Bodies and Scene Reload disabled
Reproduction steps:
1. Open the user's attached "ArmRobot.zip" project
2. Load "ArticulationRobot" scene
3. Go to Edit -> Project Settings
4. Click "Editor" and ensure that "Reload Scene" is disabled
5. Enter Play mode
6. If the crash did not occur, re-enter Play mode
-- Observe the crash
Reproducible with: 2020.2.0a21, 2020.1.4f1
Could not test with: 2018.4.26f1, 2019.4.9f1, 2020.1.0a14 (No Articulation Body Component), 2020.1.0a1-2020.2.0a7 and 2020.1.0a15-2020.1.0b7 (because of case 1220333 crash)
Notes:
- the crash most often occurs on 2-4 attempt
- sometimes an assertion message appears before the crash: Assertion failed on expression: 'm_Link'
Top 5 lines of the stack trace:
0x00007ff68af1a8a1 (Unity) Unity::ArticulationBody::HierarchicalDestruction
0x00007ff68af1a8a1 (Unity) Unity::ArticulationBody::HierarchicalDestruction
0x00007ff68af1a4f5 (Unity) Unity::ArticulationBody::HandleChangedParentInternal
0x00007ff68af1d28f (Unity) Unity::ArticulationBody::RemoveFromManager
0x00007ff68c3729d0 (Unity) EditorSceneManager::ResetOpenScenes
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
Resolution Note (fix version 2020.2):
Fixed in: 2021.1.0a10
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.1f1