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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2020.3):
Fixed in: 2020.3.31f1