Search Issue Tracker
Fixed
Fixed in 2020.3.47f1, 2021.3.22f1
Votes
2
Found in
2020.3.33f1
2021.3.5f1
2022.1.6f1
Issue ID
UUM-1510
Regression
Yes
"NullReferenceException" error is thrown when entering the Play Mode with >=2 open Inspectors and Canvas GameObject is selected
How to reproduce:
1. Create a new Unity project
2. In the Scene add "Canvas" (GameObject->UI->Canvas)
3. Open the Inspector (Window->General->Inspector)
4. Open second Inspector (Right-click on the Inspector's tab->Add Tab->Inspector)
5. In the Hierarchy select the "Canvas" GameObejct
6. Enter the Play Mode
Expected results: No errors are thrown
Actual results: "NullReferenceException" error is thrown
Reproducible with: 2020.3.2f1, 2020.3.33f1, 2021.2.19f1, 2022.1.0b15
Not reproducible with: 2019.4.37f1, 2020.3.1f1, 2022.2.0b9
Full error:
NullReferenceException: Object reference not set to an instance of an object
UnityEditor.PropertyEditor.DrawEditors (UnityEditor.Editor\[] editors) (at <780782bc035845f9909cebbd4c983ae3>:0)
UnityEditor.PropertyEditor.RebuildContentsContainers () (at <780782bc035845f9909cebbd4c983ae3>:0)
UnityEditor.InspectorWindow.RedrawFromNative () (at <780782bc035845f9909cebbd4c983ae3>:0)
-
synthc
May 03, 2022 20:33
This will happen for me when anything with a canvas renderer is selected, not just a Canvas object.
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
- ArgumentOutOfRangeException when manipulating the Project Settings search bar
- [Linux] Touch freezes in Player when any mouse button is clicked
- UnityEngine.Rendering.Volume.OnEnable() is called twice before OnDisable() creating multiple copies of the same volume when a volume is enabled right after Domain Reload when entering Play Mode
- Hinge Joint transforms are reset when toggling the "useMotor" property
- Motion Vector texture reports incorrect Mesh data when Mesh is coming from off-screen
Resolution Note (fix version 2021.3.22f1):
The warning is not shown anymore. The problem is already resolved in newer versions thanks to better implementation of EditorActivityTracker lifecycle.
Resolution Note (fix version 2020.3.47f1):
The warning is not shown anymore. The problem is already resolved in newer versions thanks to better implementation of EditorActivityTracker lifecycle.