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
- Rigidbody2D.Slide API does not have the needed configuration when creating a 2D Top-Down character controller
- Opening reference for "Playables"component redirects to a missing page
- Sprite Renderer image is changed when switching Mask Interaction and changing Sprite to a shared Sprite
- An unsigned integer is not compared with an integer correctly in player when using IL2CPP backend
- Graphical artifacts are being rendered in Scenes that are loaded during run-time when GPU Resident Drawer is turned on
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.