Search Issue Tracker
Fixed in 2020.1.X
Votes
0
Found in
2019.2.0b2
2019.4
2019.4.7f1
Issue ID
1285032
Regression
Yes
[WebGL] CachedXMLHttpRequest freezes the Player when there's network latency
How to reproduce:
1. Open the attached project's Scene labeled "SampleScene"
2. Make a WebGL build
3. Host the WebGL build
4. Open the WebGL built Player in a browser
5. In the browser, open DevTools (F12 shortcut)
6. Navigate to the Network tab
7. Open the Network Throttling Profiles
8. Click "Add custom profile" and input latency (make it between 5000-10000ms to see the result better)
9. Go back to the Network tab
10. Enable the "Disable cache" option
11. Select your custom Network Throttling Profile
12. In the WebGL Player, click the "Download" button
Expected result: Player doesn't freeze
Actual result: Player freezes when there's Network latency
Reproducible with: 2019.2.0b2, 2019.4.9f1
Not reproducible with: 2018.4.28f1, 2019.2.0b1, 2019.4.10f1, 2019.4.13f1
Couldn't test with: 2020.1.10f1, 2020.2.0b8, 2021.1.0a1 (Couldn't find an equivalent option for CachedXMLHttpRequest on the new WebGL Template)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note (fix version 2020.1):
Fixed in Unity 2019.4.10f1 and above