Search Issue Tracker
Won't Fix
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
6000.3.0a1
6000.4.0a1
6000.5.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)
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
- “+” button does nothing and has no functionality when clicked in Human Template "Bone Template" list
- Solid gray or black areas are present when using ShaderGraph with Custom Function nodes without manual reimport
- The Multiplayer Play mode tool doesn't see the list of Play Mode scenarios when using 6000.3.x
- Input field does not update when selecting the same input field after previous input was canceled
- No warning thrown when modifying array size while editing multiple objects
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.