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
- 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
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).