Search Issue Tracker
Won't Fix
Votes
1
Found in
2019.1.0b6
Issue ID
1136255
Regression
Yes
[WebGL] Using Emscripten eliminates variables and using LLVM bitcode causes freeze after Splash Screen with error
Reproduction steps:
1. Open "1136255" project
2. Build and Run for WebGL
3. Open Developers Console
4. Notice error "Input Manager initialize..."
Expected Result: WebGL player goes beyond the Splash Screen
Actual Result: WebGL player freezes after Splash Screen with an error
Reproduced with: 2019.2.0a9, 2019.1.0b8
Did not reproduce on: 2018.3.10f1, 2017.4.24f1
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
- Keywords on Material Variants aren't automatically saved when changed on original Material through Shader Graph
- Light Probes get baked when calling LightProbes.Tetrahedralize
- Shadows flicker and cause visual artifacts when modifying a GameObject's bounds using Swizzle (Y Mask) and Sine Time nodes
- [WebGL] Frame rate drops by 5-20 fps when moving cursor or touch input in the Player
- Light bleeds when using box shaped spotlight with specific Emission Range values
Resolution Note:
This bug relates to building with multithreaded C# scripts, but unfortunately multithreaded C# scripts are not yet supported in Unity multithreading, so closing as WontFix for now. We are looking towards adding support for multithreading C# scripts in the future, but currently that is not yet supported.