Search Issue Tracker

Fixed

Fixed in 6000.0.53f1, 6000.1.11f1, 6000.2.0b9, 6000.3.0a2

Votes

0

Found in

6000.0.43f1

6000.1.0b11

6000.2.0a7

6000.3.0a1

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

Add comment

Log in to post comment