Search Issue Tracker
Fixed in 2022.3.59f1
Fixed in 2023.3.X
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
- 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 (fix version 2022.3.59f1):
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-53120
Resolution Note (fix version 2023.3):
Fixed by https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-53120