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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
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.