Search Issue Tracker
Duplicate
Votes
13
Found in
2017.3.1f1
Issue ID
1034639
Regression
No
[WebGL][Chrome] game freezes after switching the browser tabs
To reproduce:
1. Open the project, attached by the user (link in the edit)
2. Build and run for WebGL
3. In the build, switch the tabs back and forth a couple of times
4. Observe that the game freezes
Expected: the game doesn't freeze when switching between tabs
Reproduced in 2017.3.1f1, 2017.4.2f2
Could not reproduce in later and earlier versions due to shader and other errors in the console which prevents the building of the project completely
-
Walkure
Jul 31, 2018 14:17
I found some steps :
1) open Web-GL game
2) open console (f12) only for fast un-focus
3) goto other page ( sometimes i reload different pages )
4) return and click on game canvas -> freeze 80% chance.
But our game still write logs to console and handle click by screen =)
But render is disabled.Fix : canvas resizing helps but it very bad idea =)
-
Walkure
Jul 31, 2018 13:33
We have the same problem with a Unity WebGL build with Unity 2018.2.0f2
-
FernandoChen
Jun 12, 2018 05:17
Same problem here after we upgrade from 5.6.4p1 to 5.6.6f2.
Seems to happen only on Chrome 67, can't reproduce on Chrome 66. -
PSchaussPlaya
May 31, 2018 14:02
We have the same problem with a Unity WebGL build (WebAssembly) with Unity 2018.1.0f2. So this is still an issue.
I seems to happen when switching to another tab for some time and then switching back.
Interesting observation: All rendering seems to be completely frozen (our game is UI only) but buttons seem to be still clickable because related sounds are still played. So I assume that the game is still running normally and that only the rendering is broken.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
This is a duplicate of issue #1088870