Search Issue Tracker
Fixed
Fixed in 6000.0.59f1, 6000.2.7f1, 6000.3.0b4, 6000.4.0a2
Votes
2
Found in
6000.0.57f1
6000.2.3f1
6000.3.0a6
6000.4.0a1
Issue ID
UUM-117267
Regression
No
Error “NullReferenceException: Object reference not set to an instance of an object“ is present when the UI Toolkit Debugger window is docked and inactive on Editor launch
Reproduction steps:
1. Open the attached project "ReproProj"
2. Open Window > UI Toolkit > Debugger
3. Dock the “UI Toolkit Debugger” tab next to another panel (e.g., dock it with the Inspector).
4. Click another tab (e.g., “Inspector”) so that “UI Toolkit Debugger” is docked but not the visible/active tab.
5. Close the Editor
6. Reopen the same project
Expected result: No Errors exist
Actual result: Error “NullReferenceException: Object reference not set to an instance of an object“ is present
Reproducible with: 6000.0.57f1, 6000.2.3f1, 6000.3.0a6
Testing environment: Windows 10 Enterprise 21H2
Not reproducible on: No other environment tested
Notes:
- The exception spam immediately stops once the “UI Toolkit Debugger” tab is brought to the foreground (made the active/visible tab)
- The issue does not occur if the UI Toolkit Debugger window is closed before launch, or if it is the active/visible tab when the Editor opens.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Unity CIL Linker fails on Player build when persistent listeners have "<" and ">" in their XML attribute names
- ”Lighting data asset ‘LightingData’ is incompatible with the current Unity version…” warnings are thrown when saving Indoors (URP) and Outdoors (URP) Scenes as Scene Templates
- [iOS] The screen blinks when transitioning from custom to Unity splash screen
- [macOS] ”Ignoring depth surface load action as it is memoryless” warnings are thrown when taking Game View Snapshot
- UI Builder Inspector scrolls back up when changes on an expanded but not fully displayed Inspector tab are saved
Add comment