Search Issue Tracker
By Design
Votes
0
Found in
2018.4
2019.3.10f1
2019.4
2020.1
2020.2
Issue ID
1252396
Regression
No
Simple CustomEditor scripts cause significant performance impact
How to reproduce:
1. Open the attached 'project-1252396.zip' project
2. In the Hierarchy window select 'Test Object'
3. Observe the values of 'Test Component (Script)'
Expected result: less calls are made to OnInspectorGUI() and ISerializationCallbackReceiver() per frame
Actual result: multiple unnecessary calls are made to OnInspectorGUI() and ISerializationCallbackReceiver() per frame
Reproducible with: 2018.4.23f1, 2019.4.1f1, 2020.1.0b12, 2020.2.0a14
Note: entering Play mode, changing value in the Inspector increases the number of calls to the mentioned methods per frame
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
- NullReferenceException is thrown when adding a Blur Renderer Feature
- [Linux] Dropdown Menus are filled with empty entries when the Menu intersects with the Editors borders
- [HDRP] [Metal] Tiled artefacts when using DRS
- [HDRP] Empty template starts with incorrect Physically Based Sky ground
- Big chunk of "Untracked" memory in the Memory Profiler screenshot when a custom .obj file is loaded while in Play Mode
Resolution Note (2020.2.X):
There is a method to check if there has been any changes done to the Monobehavior outside of the editor, without calling setDirty. This peice of code runs every frame and hence the number of calls to the OnBeforeSerialize method. This issue is likely by Design