Search Issue Tracker
Fixed in 2021.2.X
Fixed in 2021.1.X
Votes
0
Found in
2019.4
2020.1
2020.1.6f1
2020.2
2021.1
Issue ID
1292133
Regression
No
StackOverflowException when using UIElements Default Inspector and Nested UIToolkit PropertyField in PropertyDrawer
How to reproduce:
1. Open attached project "Case1292133_StackOverflow.zip"
2. Enter Internal mode (type "internal" in Help/About Unity Window)
3. Select "Example" asset in the Project Window
4. Select "Use UIToolkit Default Inspector" in Inspector settings (more options icon in the top right corner)
Expected result: No exception is thrown
Actual result: StackOverflow exception in the Console
Reproducible with - 2019.4.15f1, 2020.1.17f1, 2020.2.0b14, 2021.1.0a10
Could not test with - 2018.4 (Editor errors)
Notes:
The editor crashes when "ReadOnly" property is added to the script after "Use UIToolkit Default Inspector" option was selected
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a3
Resolution Note (fix version 2021.1):
Fixed in 2021.1.24f1