Search Issue Tracker
Active
Under Consideration for 1.22.X, 2.3.X
Votes
0
Found in [Package]
1.22.3
2.3.1
Issue ID
ADDR-3802
Regression
No
Multiple types of errors are thrown when the removal of an Addressables Node from a Graph is undone
How to reproduce:
1. Open the “BugTest.zip“
2. Open the “SampleScene“
3. Enter and exit the Play Mode
4. Select the InsideAddressables Asset in the “Assets/Graphs/InsideAddressables“ directory
5. Click the “Edit Graph“ button to open the InsideAddressables Node Graph
6. Remove the “Remove me“ node from the Graph in the InsideAddressables window and undo
7. Select the “Remove me“ node in the InsideAddressables window
8. Observe the Console
Expected result: “MissingReferenceException“, “ArgumentException“ and another error are logged in the Console
Actual result: No errors are thrown in the console
Reproducible in: 1.22.3 (2021.3.45f1, 2022.3.51f1), 2.3.1 (6000.0.25f1)
Reproduced on: Windows 11 Pro (23H2),
Not reproduced on: No other environment tested
Notes:
- The three types of errors are:
▶ “MissingReferenceException: The object of type 'EasyNode' has been destroyed but you are still trying to access it.“
▶ “ArgumentException: Getting control 1's position in a group with only 1 controls when doing repaint“
▶ “You cannot call GetLast immediately after beginning a group.“
- Sometimes step 6 has to be done multiple times to invoke the issue
- Errors are thrown constantly while the “Remove Me“ node is selected
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Disabled assets in Import Unity Package window aren't tracked but count as being selected by user
- [Windows] Crash on GetManagerFromContext when video is playing and creating High Definition 3D Projects after FMOD failed to switch back to normal output Error appeared
- GC Alloc produced when adding items to MultiColumnListView with Auto Assign Binding
- Mouse and Pointer Events are called incorrectly in ScrollView with XRUIInputModule
- Memory leak occurs when repeatedly minimizing and maximizing the UI Builder window
Add comment