Search Issue Tracker
Fixed
Votes
0
Found in
2022.3.10f1
2023.1.16f1
2023.2.0b12
2023.3.0a8
Issue ID
UUM-52904
Regression
No
The Profiler can't be connected in WebGL builds when building in multithreading mode
How to reproduce:
1. Open the user-attached project “webgl-multithreading”
2. Open the “Build Settings”
3. Make sure “Autoconnect Profiler” is selected and “Build And Run” the project
4. Observe the build results
Expected result: The Profiler is connected to the build
Actual result: The Profiler fails to connect to the build with the “[1] The message header is corrupted and for security reasons connection will be terminated.” error
Reproducible with: 2022.3.10f1, 2023.1.16f1, 2023.2.0b12, 2023.3.0a8
Can’t test with: 2021.3.31f1 (Unable to build the project due to unfixable compilation errors)
Reproducible on: Windows 11 Pro
Not reproducible on: No other environment tested
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
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note:
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-53120