Search Issue Tracker
Active
Under Consideration for 6000.0.X, 6000.1.X, 6000.2.X
Votes
0
Found in
6000.0.43f1
6000.1.0b11
6000.2.0a7
Issue ID
UUM-101218
Regression
Yes
Player unresponsive when building a specific project with Autoconnect Profiler enabled
How to reproduce:
1. Open the attached “IN-96534.zip” project
2. Open the Build Profiles window (File > Build Profiles)
3. Ensure Development Build and Autoconnect Profiler settings are enabled
4. Build and Run the project
5. Switch to the Profiler window (ALT + TAB)
6. Observe that no data is displayed
7. Wait 10-20 seconds
8. Switch back to the built application
9. Observe the result
Expected result: Profiler data is logged and application runs without issues
Actual result: No profiler data is logged and application is not responding
Reproducible in: 6000.0.17f1, 6000.0.43f1, 6000.1.0b11, 6000.2.0a7
Not reproducible in: 2022.3.45f1, 2022.3.60f1, 6000.0.16f1
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Note:
- The issue does not reproduce with the Mono scripting backend
- The issue does not reproduce when the “_drawDistance” value in the “MRE.cs” script is set to 40 or less
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- "Create Empty Child" Option Creates Root Object When No Parent Is Selected
- Freeze/Crash when entering Play Mode in a specific project
- Lack of documentation regarding VFX Ray Tracing support
- Shader properties do not appear on the GameObject when switching ShaderGraphs during runtime in the Player
- Multiple '-' symbols are allowed to appear in a row when inputting '.' into a non-decimal numeric field
Add comment