Search Issue Tracker
Duplicate
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
-
Resolution Note:
Thank you for reporting a bug to Unity.
This bug is a duplicate of another one that we already have in our bug tracking system https://unity3d.atlassian.net/servicedesk/customer/portal/2/IN-55797
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.
Duplicate of https://issuetracker.unity3d.com/product/unity/issues/guid/UUM-53120
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
This is a duplicate of issue #UUM-53120