Search Issue Tracker
Fixed in 2019.3.X
Votes
0
Found in
2018.1.0a1
2018.3.0a1
2018.3.0f2
2019.1.0a1
2019.2.0a1
Issue ID
1116630
Regression
No
Crash on ObjectUndo::Restore when undoing after calling Undo.RegisterCompleteObject(object, name)
How to reproduce:
1. Open the "Undo_Crash.zip" project
2. Window > Tools > Reformer
3. Select "Cube" prefab in the object field
4. Select any game object in the Hierarchy
5. Press "Replace"
6. Press CTRL + Z
Actual result: Unity crashes.
Reproducible with: 2019.2.0a2, 2019.1.0a15, 2018.3.3f1, 2018.1.9f2.
-----------------------------------------
Fixed in: 2019.3.0a7
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 2019.3):
The use of DestroyImmediate(object) within Undo groups is undefined behaviour as it will permanently destroy the asset.
It is recommended to always use Undo.DestroyObjectImmediate(object) to ensure that the destroyed object is stored on the undo buffer and can be fully restored.
Fatal error message added.