Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
1
Found in
2019.3.10f1
2019.3.14f1
2020.2
Issue ID
1250419
Regression
Yes
Editor crashes when unlocking Inspector with PropertyInfo.SetValue function
How to reproduce:
1. Open the attached project's Scene labeled "SampleScene"
2. In the Project Window, select the "NewWearableBody" ScriptableObject
3. In the Inspector, click the "Locate Sprite" button
4. Click the "Cancel Locate Sprite" button
Expected result: Editor doesn't crash when unlocking Inspector with PropertyInfo.SetValue function
Actual result: Editor crashes when unlocking Inspector with PropertyInfo.SetValue function
Reproducible with: 2019.3.10f1, 2019.3.15f1, 2020.1.0b9, 2020.2.0a12
Not reproducible with: 2018.4.23f1, 2019.3.9f1
Couldn't test with: 2017.4.40f1 (Script doesn't unlock the Inspector)
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
- “[Worker0] Could not generate preview image“ error when opening macOS native plugin in the Inspector with Architecture to build for set to ARM 64-bit
- [iOS] Application.absoluteURL is empty on Awake/Start when opening via deep link with Splash Screen disabled
- Crash on MemoryManager::Deallocate when rapidly calling Addressables.LoadAssetAsync
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0a20
Resolution Note (fix version 2020.1):
Fixed in Unity 2020.1.4f1
Resolution Note (fix version 2019.4):
Fixed in Unity 2019.4.15f1