Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2018.3.0a1
2019.1.0a1
2019.2.0a1
2019.3.0a1
2019.3.0a8
Issue ID
1171484
Regression
No
CustomEditor instance is created if called when the Inspector window is locked on another object
Repro steps:
1. Open attached "case_1171484-2019.3Test.zip"
2. Create a second Inspector tab
3. In the Project window, select "SampleScene.unity"
4. With the object still selected, lock the new Inspector tab
5. Delete the unlocked Inspector tab
6. In the Project window, select and deselect "DefaultAsset.objConfig"
7. Open Console
Expected results: CustomEditor is not enabled or disabled
Actual results: one instance of CustomEditor is enabled and disabled
Reproducible with: 2017.4.30f1, 2018.4.5f1, 2019.1.12f1, 2019.2.0f1, 2019.3.0a11
Notes: if we delete the locked Inspector tab instead of the unlocked one, lock it having selected "SampleScene.unity", and repeat steps 6-7, no instances of the CustomEditor are detected
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 (2019.3.X):
low priority for our team, unlikely to be fixed for the moment.