Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2019.1.0a1
2019.1.0f1
2019.2.0a1
2019.3.0a1
Issue ID
1173148
Regression
No
[WebGL] Unity Player never recovers from WebGL context loss
How to reproduce:
1. Open the attached project ("")
2. Make a WebGL build
3. Host and run it
4. Focus the game window and press "Space" to trigger the WebGL context loss
Expected results: Unity Player recovers from WebGL context loss
Actual results: Unity Player does not recover from WebGL context loss
Reproducible with: 2017.4.31f1, 2018.4.5f1, 2019.1.13f1, 2019.2.0f1, 2019.3.0a11
Tested with:
Google Chome Version 76.0.3809.87 (Official Build) (64-bit)
Firefox 68.0.1 (64-bit)
Microsoft Edge 42.17134.1.0
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
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note (2020.1.X):
To handle context loss properly on WebGL requires feature level work. Already tracked separately.