Search Issue Tracker
Not Reproducible
Votes
0
Found in
2022.3.63f1
6000.0.51f1
6000.1.7f1
6000.2.0b5
Issue ID
UUM-109226
Regression
No
Build becomes unresponsive when enabling "Deep Profiling Support" and "Autoconnect Profiler" build options in a specific project
How to reproduce:
1. Open the attached “IN-102715” project
2. Open the Build Settings window (File → Build Settings)
3. Make sure the “Development Build”, “Deep Profiling Support” and “Autoconnect Profiler” options are enabled in the Build Settings window
4. Build and run the project
5. Observe the built project
Expected result: The build does not become unresponsive
Actual result: The build becomes unresponsive
Reproducible with: 2022.1.0b13, 2022.3.63f1, 6000.0.51f1, 6000.1.7f1, 6000.2.0b5
Could not test with: 2022.1.0a1, 2022.1.0b12 (A lot of 'Does not contain definition' errors)
Reproduced on: Windows 10, Windows 11
Not reproduced on: No other environment tested
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
- UI Toolkit meshes are fully rendered and rasterized when opacity is 0
- Light rendering artefacts appear in the Editor when assigning unsupported 3D Custom Render Texture in Camera’s Output Texture, unclearable errors and warnings spammed
- Memory leak when running a test with "GfxThreadingMode" set to "SplitJobs"
- Loading Unloaded unsaved Scene throws “ArgumentException” error in the Console
- Crash on std::__1::__tree_const_iterator when opening the Build Profiles window in a specific project
Resolution Note:
I'm not able to reproduce this issue, I've tried on Mac (6000.2.0b5) and Windows (6000.2.0b4) and both seems to result in the build running correctly. If you are still able to reproduce can you have a look at the steps and see if there is something missing. Also could you see if anything is output in the player.log. If you could produce a call stack this might also help