Search Issue Tracker
Fixed
Fixed in 2023.1.0b11, 2023.2.0a8
Votes
6
Found in
2023.1.0b3
2023.2.0a2
Issue ID
UUM-26990
Regression
Yes
Performance degrades when profiling in newer Editor versions
How to reproduce:
1. Create a new project
2. Enter Play Mode
3. Open the Profiler window (Window → Analysis → Profiler)
4. Change the profiling mode to Edit Mode
5. Stop the recording of the Profiler
6. Select any point in the profiled section
Expected result: Consistent performance between Editors
Actual result: Performance is slower and uses double the allocated resources
Reproducible with: 2023.1.0a20, 2023.1.0b3, 2023.2.0a2
Not reproducible with: 2020.3.45f1, 2021.3.19f1, 2022.2.7f1, 2023.1.0a19
Reproduced on: macOS Ventura 13.1 (Intel), Windows 10 - User Reported
Note: Related Forum thread - [https://forum.unity.com/threads/regression-game-view-eating-x10-more-cpu.1377261/|https://forum.unity.com/threads/regression-game-view-eating-x10-more-cpu.1377261/]
-
laurentlavigne
Feb 15, 2023 22:10
2023 is much slower than 2022 even without profiler.
So the degradation that's slowly eroded the editor and was somewhat slowed down is back in a big way. -
Kamyker
Feb 14, 2023 08:33
"WHEN PROFILING" is a bit of a stretch, performance degrades also when not profiling.
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
Resolution Note (fix version 2023.1.0b11):
Improve Text performance for both IMGUI and UITK.