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
- 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 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.