Search Issue Tracker
Won't Fix
Won't Fix in 2022.2.X
Votes
0
Found in
2022.2.0a3
Issue ID
UUM-6731
Regression
Yes
Significant drop in performance when Profiling with Deep Profile on and something is selected in Related Data
Steps to reproduce:
1. Create a new project or open and existing one
2. Open Profiler
3. Set Profiling mode to Editor
4. Toggle Live profiling on
5. Search for gc and select any GC.Alloc call
6. In the details dropdown select Related Data
7. Enable Deep Profile
8. Select the any line in Details window
9. Hover over Related Data/Profiler Data windows
Expected result: Profiler and Editor performance doesn't decrease significantly
Actual result: Profiler and Editor slows down so much that it's basically frozen
Reproducible with: 2021.1.0a6, 2021.2.10f1, 2022.1.0b6, 2022.2.0a3
Not reproducible with: 2020.3.28f1, 2021.1.0a5 (has different issues, see edits for more info)
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:
The issue will be addressed as part of the profiler window upgrade to UI toolkit.
Resolution Note (2022.2.X):
The issue will be addressed as part of the profiler window upgrade to UI toolkit.