Search Issue Tracker
By Design
Votes
0
Found in
2021.3.35f1
2022.3.20f1
2023.2.12f1
2023.3.0b9
Issue ID
UUM-67208
Regression
No
Profiler disconnects from WebGL Player when it gets clicked on in URP
Reproduction steps:
1. Open the attached “ProfilingIssue.zip” project
2. Open the Profiler Window (Window > Analysis > Profiler)
3. Build and Run for WebGL
4. Interact with the Player in the Browser
5. Observe that the Profiler Window has connected to the Player
6. Click on the Profiler Window
Expected result: The Profiler target is the Player and “Autoconnected Player” text is visible
Actual result: The Profiler target changes to “Play mode” or “Edit mode”
Reproducible with: 2021.3.35f1, 2022.3.20f1, 2023.2.12f1, 2023.3.0b9
Reproducible on: Windows 11
Not reproducible on: no other environment tested
Note:
- Only reproduces in URP
- Also reproduces with Memory Profiler
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
- Mouse input is registered incorrectly in Custom RP when downscaling Render Target and rendering Overlay UI before final upscale
- Time.deltaTime is locked to the display's refresh rate when the built Player is moved to a Secondary Display and Windowed Mode is used
- Crash on RaiseException when importing a specific asset
- Crash on RaiseException when opening a specific project
- DownloadHandlerScript.CompleteContent is called twice when building for WebGL
Resolution Note:
This is as designed. The Project setting 'Run in Background' has not been set, so when focus is moved away from the player it stops the connection to the profiler. The Profiler doesn't know if the connection will be resumed, so changes the text from 'Autoconnected'. If you click back on the player then the profiler automatically re-connects so you can continue collecting data (and the profiler changes the text back).