Search Issue Tracker
Fixed in 2020.3.X
Votes
0
Found in
2020.2
2020.3
2020.3.24f1
Issue ID
1408562
Regression
No
Editor performance drops when a Game Object with a Custom Editor has its element expanded
Reproduction steps:
1. Open the attached project: "1408562.zip"
2. In the Project window go to Assets > MackySoft > MackySoft.SerializeReferenceExtensions > Example
3. Open "Example" Scene
4. In the Profiler window, set Target Selection to Editor and Record profiling information
5. Select the "Example" Game Object in the Hierarchy window
6. In the Inspector window under "Commands" expand "Element 0"
7. Observe the Profiler
Expected result: Expanding elements within the Inspector window should not reduce performance
Actual result: Performance drops after expanding the elements
Reproducible with: 2020.2.0b3, 2020.3.30f1
Not reproducible with: 2019.4.37f1, 2020.2.0b2, 2020.3.31f1, 2020.3.33f1, 2021.2.19f1, 2021.3.1f1, 2022.1.0b15, 2022.2.0a9
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
- HDRP 6-way VFX Shader is lit incorrectly when World coordinates are used
- 2D Sprite Renderer in front is affected by Sprites in the background when using Sorting Layers and a Shadow Caster 2D with Self Shadow
- Modifying UI Prefab child's Height only confirms the first 1 or 2 digits when the Scene is newly opened or the Prefab is newly created
- ProfilingSampler.Get() returns null and makes the Player only render black when building a Release Build
- Search text field visual controls for the Path binding in an Input Actions Asset is misaligned
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.31f1