Search Issue Tracker
Won't Fix
Won't Fix in 2022.3.X
Votes
0
Found in
2022.3.69f1
Issue ID
UUM-135829
Regression
No
Crash on UndoManager::RegisterUndoInternal when applying added GameObjects to a Prefab
Reproduction steps:
1. Open the attached project ("IN-134326_Repro")
2. Check "Work Offline" in "Project Settings -> Version Control"
3. Open scene "00_Scenes/1_SinglePlayer/02_Night"
4. In the Scene Hierarchy, duplicate any prefabs in "[Environment] -> NightLevel"
5. Make sure the duplicated prefabs are selected, right-click and select "Added GameObjects -> Apply To Prefab ..."
6. If it does not crash, repeat steps 4 and 5
Expected result: The added GameObjects gets applied to the prefab
Actual result: The Editor crashes
Reproducible with: 2022.3.72f1
Not reproducible with: 6000.0.68f1, 6000.3.10f1, 6000.4.0b10, 6000.5.0a7
Reproducible on: Windows 11
Not reproducible on: No other environment tested
Stacktrace:
0x00007ff7a4f2d5d4 (Unity) UndoManager::RegisterUndoInternal
0x00007ff7a4f2ddd6 (Unity) UndoManager::RegisterUndoToFrontOfUndoQueue
0x00007ff7a4f1343c (Unity) RecordObjectCreationToFrontOfUndoQueue
0x00007ff7a353ce18 (Unity) Undo_CUSTOM_RecordObjectCreationToFrontOfUndoQueue
0x000001b2229a47fc (Mono JIT Code) (wrapper managed-to-native) UnityEditor.Undo:RecordObjectCreationToFrontOfUndoQueue (UnityEngine.Object,string)
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:
Thank you for reporting a bug to Unity.
We are unable to fix this issue in 22.3 as it is no longer a supported release version. The suggested course of action is to upgrade to a newer version of Unity, as the issue is no longer reproducible in later versions.
Today we will be closing this case. Thank you again for taking the time to report this issue.
Resolution Note (2022.3.X):
Thank you for reporting a bug to Unity.
We are unable to fix this issue in 22.3 as it is no longer a supported release version. The suggested course of action is to upgrade to a newer version of Unity, as the issue is no longer reproducible in later versions.
Today we will be closing this case. Thank you again for taking the time to report this issue.