Search Issue Tracker
Fixed in 2023.1.0b11
Fixed in 2023.1.X, 2023.2.X, 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/
Comments (2)
-
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
- 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 2023.1):
Improve Text performance for both IMGUI and UITK.