Search Issue Tracker
Fixed
Fixed in 2020.3.42f1, 2021.3.8f1, 2022.1.12f1, 2022.2.0b3, 2023.1.0a4
Votes
4
Found in
2022.1.1f1
2022.2.0a9
2023.1.0a1
Issue ID
UUM-798
Regression
Yes
[WebGL] Profiler does not autoconnect on WebGL builds
How to reproduce:
1. Create new project
2. Open build settings, switch to WebGL and enable Autoconnect profiler setting
3. Build and run
4. Observe Profiler does not connect automatically
5. Observe Console
Warning spam: Connection X is no longer valid. Calling auto disconnect.
Reproduced with: 2022.1.0b1
Does not reproduce with: 2022.1.0a16
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
- Search field in UI Builder's Library has no character limit
- Changing the value in UI Builder by dragging increases it by a few thousand points when reaching the borders of the screen
- ARM64 architecture DLL incorrectly copied instead of x64 when building for Windows x64
- Crash on TypeTreeIterator::GetNode when opening a specific folder
- Crash on WriteSerializedAssetsV2 when (re)entering the Play Mode in a specific project when IEnumerator Start() is used
devluz
Nov 05, 2022 05:45
Is this really fixed in any version? I have the same issue on 2021.3.12f
The console logs:
Connection 14 is no longer valid. Calling auto disconnect.
WebGL warning: clientWaitSync: ClientWaitSync must return TIMEOUT_EXPIRED until control has returned to the user agent's main loop. (only warns once) 2
Firefox can’t establish a connection to the server at ws://192.168.1.3:54998
This this a new bug or the same?