Search Issue Tracker
Fixed
Fixed in 2022.3.42f1, 6000.0.13f1, 7000.0.0a1
Votes
2
Found in
2022.3.29f1
6000.0.2f1
Issue ID
UUM-71750
Regression
Yes
Profiler does not profile after building the Project with Autoconnect Profiler Option enabled
How to reproduce:
1. Create a new Project
2. Open Build Profiles Window (File -> Build Profiles)
3. Build and Run the Project with Development Build and Autoconnect Profiler Options enabled
4. After running the Project minimize the built Project window
5. Observe the Profiler
Expected result: The Profiler should have data on Performance
Actual result: No Profiling Occurs
Reproducible with: 2022.3.29f1, 2022.3.37f1, 6000.0.2f1
Not reproducible with: 2022.3.22f1, 2023.3.0a8
Regressed versions: 2022.3.23f1, 2023.3.0a10
Reproduced on: Windows 11, Windows 10, Mac Intel, Ubuntu 20
Note: The bug could be very specific to reproduce, this may differ due to the every computer having different networking setup
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
Add comment