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
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
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.