Search Issue Tracker
Active
Under Consideration for 6000.6.X
Votes
0
Found in
6000.6.0a2
Issue ID
UUM-137979
Regression
No
Renaming issues when clicking a selected node and immediately deleting it.
There are two issues that can happen when deleting a node that is in the process of entering its rename mode:
- Rename starts on another item, possibly where the HierarchyViewItem is recycled.
- There are errors thrown in the console if there is no other node that reuse this HierarchyViewItem.
Steps to reproduce:
- Create an empty scene.
- Add two game objects.
- Select the first one.
- Click it again and delete it before the renaming process starts. Renaming will start on the other game object.
- Cancel rename and select the remaining game object. If a rename starts, cancel it.
- Click it again and delete it before the renaming process starts.
- Errors are logged in the console, with the following callstack:
{noformat}
NullReferenceException: Object reference not set to an instance of an object
Unity.Hierarchy.Editor.HierarchyGameObjectHandler.Unity.Hierarchy.IHierarchyEditorNodeTypeHandler.CanSetName (Unity.Hierarchy.HierarchyView view, Unity.Hierarchy.HierarchyNode& node) (at D:/UnitySrc/u/u3/Modules/HierarchyEditor/ScriptBindings/HierarchyGameObjectHandler.bindings.cs:206)
Unity.Hierarchy.HierarchyViewItem.BeginRename () (at D:/UnitySrc/u/u3/Modules/Hierarchy/Managed/HierarchyViewItem.cs:305)
Unity.Hierarchy.HierarchyView+<>c__DisplayClass174_0.<OnClickEvent>b__0 () (at D:/UnitySrc/u/u3/Modules/Hierarchy/Managed/HierarchyView.cs:1500)
UnityEngine.UIElements.VisualElement+SimpleScheduledItem.PerformTimerUpdate (UnityEngine.UIElements.TimerState state) (at D:/UnitySrc/u/u3/Modules/UIElements/Core/VisualElementScheduler.cs:385)
UnityEngine.UIElements.TimerEventScheduler.UpdateScheduledEvents () (at D:/UnitySrc/u/u3/Modules/UIElements/Core/Scheduler.cs:386)
UnityEngine.UIElements.Panel.TickSchedulingUpdaters () (at D:/UnitySrc/u/u3/Modules/UIElements/Core/Panel.cs:1523)
UnityEngine.UIElements.UIElementsUtility.UpdateSchedulers () (at D:/UnitySrc/u/u3/Modules/UIElements/Core/UIElementsUtility.cs:179)
UnityEditor.RetainedMode.UpdateSchedulers () (at D:/UnitySrc/u/u3/Modules/UIElementsEditor/RetainedMode.cs:44)
UnityEngine.StackTraceUtility:ExtractStringFromExceptionInternal(Object, String&, String&) (at D:/UnitySrc/u/u3/Runtime/Export/Scripting/StackTrace.cs:50)
{noformat}
Actual results:
For scenario 1: renaming starts on another node.
For scenario 2: errors are thrown in the console.
Expected results:
For scenario 1: no renaming is started.
For scenario 2: no errors are thrown.
Reproducible with versions: 6000.6.0a2
Not reproducible with versions:
Can’t test with versions:
Tested on (OS): Windows 11.
Notes:
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
Add comment