Search Issue Tracker
Won't Fix
Won't Fix in 2023.1.X
Votes
1
Found in
2021.3.16f1
2022.2.2f1
2023.1.0a25
Issue ID
UUM-24687
Regression
Yes
Player stuck after display of the Unity logo when building for WebGL
Reproduction steps:
1. Open project “CurvyPackage”
2. Open scene “Untitled”
3. Build and Run for WebGL
Expected result: project is built and the scene is visible
Actual result: project is built, but the scene is not loading
Reproducible with: 2021.3.16f1, 2022.2.2f1, 2023.1.0a25
Not reproducible with: 2020.3.43f1
Reproducible on: Catalina 10.15.7 (Intel)
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
This issue was caused by a call to Parallel.For in a user script in the Curvy package. Unfortunately, C# multithreading is not supported yet for WebGL, although we are looking at adding support for this in the future.
If you want to preserve this behavior for non WebGL builds, you can conditionally compile this logic using #if UNITY_WEBGL to control whether a parallel or standard for loop is used. Lastly, please refer to the Unity WebGL documentation for more details regarding constraints that are involved when targeting WebGL builds: https://docs.unity3d.com/Manual/webgl.html.
Resolution Note (2023.1.X):
This issue was caused by a call to Parallel.For in a user script in the Curvy package. Unfortunately, C# multithreading is not supported yet for WebGL, although we are looking at adding support for this in the future.
If you want to preserve this behavior for non WebGL builds, you can conditionally compile this logic using #if UNITY_WEBGL to control whether a parallel or standard for loop is used. Lastly, please refer to the Unity WebGL documentation for more details regarding constraints that are involved when targeting WebGL builds: https://docs.unity3d.com/Manual/webgl.html.