Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2019.4.X, 2020.1.X, 2020.2.X
Votes
28
Found in
2019.1.0a12
2019.2.0a1
2019.3.0a1
2019.3.0a6
Issue ID
1165055
Regression
Yes
WebGL build throws "Threads are not enabled for this platform" error when program's built using Debug C++ Compiler Configuration
How to reproduce:
1. Open the attached project("WebGL_Test")
2. Build and run
Expected result: the program runs without errors
Actual result: "Threads are not enabled for this platform." error is thrown
Reproducible with: 2019.1.0a12, 2019.1.8f1, 2019.2.0b8, 2019.3.0a8
Not reproducible with: 2018.4.3f1
Note:
- C++ Compiler Configuration is not available before 2018.3.4f1 and 2019.1.0a12
Comments (1)
-
r3dux
Oct 21, 2021 10:03
Still present in 2020.3.18f for WebGL builds when the C++ Compiler Mode is "Debug".
Changing the C++ Compiler Mode to Release solves the issue.
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
- Motion vectors are displayed when Phong Tessellation is used on the material and Skinned Motion Vectors are enabled on the GameObject's Skinned Mesh Renderer component
- Shader Graph Enum Keywords always select last element in Entries when Stages is set to Fragment and Recursive Rendering is enabled in the Scene
- [Mac] Glitchy visual artifacts appear when moving around a scene with Sphere Handles
- Crash on memcpy_repmovs when selecting NavMesh Agent objects while in Play Mode in a specific scene
- Console shows Exception: {"error":"not found","detail":["not found"]} after opening Build History window
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0a2
Resolution Note (fix version 2020.2):
Fixed in 2020.2.0b12
Resolution Note (fix version 2020.1):
Fixed in: 2020.1.14f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.15f1