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
- Crash on UndoManager::RegisterUndoInternal when applying added GameObjects to a Prefab
- [Asset Bundles] A new bundle hash is not generated when the name of a serialized field is changed
- Icon section shows incomplete message and unusable check box in Build Profiles and Player Settings window instead of “Not applicable for this platform” for Dedicated Server Platform
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
Resolution Note (fix version 2021.2):
Fixed in 2021.2.0a3
Resolution Note (fix version 2021.1):
Fixed in 2021.1.24f1