Search Issue Tracker
Active
Under Consideration for 2022.3.X, 6000.0.X, 6000.1.X, 6000.2.X
Votes
0
Found in
2022.2.0b7
2023.1.0a9
2023.2.0a1
2023.3.0a3
6000.0.0b11
6000.1.0a7
6000.2.0a1
7000.0.0a1
Issue ID
UUM-13182
Regression
No
Inspector in "Debug" mode degrades Editor performance when an object is selected in Project Browser
How to reproduce:
1. Open the user’s attached “InspectorBug” project
2. Switch the Inspector mode to “Debug”
3. Select the “New Material” Material in the Project Browser
4. Observe the “Scripts” CPU Time Usage in the “Edit Time” Profiler
Expected result: CPU Time Usage is up to ~30 ms for each selection
Actual result: CPU Time Usage is up to ~150 ms for each selection
Reproducible with: 2022.2.0a9, 2022.2.0b7, 2023.1.0a9
Not reproducible with: 2020.3.39f1, 2021.3.9f1, 2022.1.15f1, 2022.2.0a8
Reproduced on: macOS 12.5 (Intel)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- visionOS Players are minimized when Guided Access is turned on
- Licensing Client fails to launch when opening Unity Hub
- Sprite Atlas Inspector preview disappears when entering Play mode unless SpriteAtlasMode is set to "Sprite Atlas V2 - Enabled"
- Opening reference for Audio Importer opens missing page
- [Android] SpriteAtlas gets corrupted in Player when using Late binding with SRP Batcher enabled
Add comment