Search Issue Tracker
By Design
Votes
0
Found in
2022.2.0b9
2023.1.0a12
Issue ID
UUM-15643
Regression
No
WebGL Build throws returns runtime errors when ran in native multi-thread mode
Reproduction steps:
- Open the attached project
- Switch the Target Platform to WebGL (File > Build Settings > WebGL > Switch Platform)
- Build And Run the project
- Observe the Errors in the Browser’s developer console (F12)
Expected result: The WebGL Build doesn’t produce any errors and runs smoothly
Actual result: The WebGL Build throws a lot of errors and doesn’t run
Reproducible with: 2022.2.0b9, 2023.1.0a12
Could not test with: 2020.3.40f1, 2021.3.11f1, 2022.1.18f1 (Couldn’t build due to WebGL Build errors)
Reproducible on: Windows 10 (21H2)
Note: If the browser throws a “Your browser does not support multi-threading” error, run the build using the attached emrun.py python script from the build folder using the command line/terminal with the “python emrun.py index.html --no_browser --port 8000” command
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
Resolution Note:
Yes, the problem was in the incorrect user implementation of C++ std:thread, is not a Unity problem, the customer is still reviewing the suggestion provided.