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
- [URP] Invalid update of shader stripping settings
- [HDRP] Errors on Shader stripper that do not stripp shaders.
- Usage of Adaptive Probe Volumes throws a lot of IndexOutOfRangeException and Assertion Failed errors
- Prefab overrides don't recover missing managed references
- Trail Renderer visual doesn't match the positions of vertices when they have been offset
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.31f1