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
- Uninitialized variable warning appears in the Inspector of a custom shader when the variable is initialized
- "Failed creating toolbar element from ID..." error is thrown when resetting the Scene view Overlay layout while an Asset Transformer Toolbox overlay is active
- Entity ID for Font Assets is serialized twice which throws an error when using Debug Inspector
- Play Mode can be entered when disabling Adaptive Performance and pressing either the Play Mode button or the keyboard shortcut to enter Play Mode before recompilation leading to errors and warnings thrown
- Parent ListView element also becomes selected when inner ListView element is selected
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.