Search Issue Tracker
By Design
Votes
0
Found in
2017.4.0f1
2018.4.0f1
2019.2.0a1
2019.2.5f1
2019.3.0a1
2020.1.0a1
Issue ID
1185256
Regression
No
WebGL builds have performance issues when many parallel UnityWebRequests are sent
How to reproduce:
1. Open the attached project ("case_1185256-loadingTest2019.zip")
2. Change targeted platform to WebGL
3. Make a WebGL build
4. Include the "Assets/pngs" folder in the build folder
5. Run the build and press the "Load" button
Expected results: Images are loaded asynchronously without noticeable performance drop
Actual results: Build has a noticeable performance drop while loading the images
Reproducible with: 2017.4.32f1, 2018.4.10f1, 2019.2.7f2, 2019.3.0b5, 2020.1.0a6
Comments (1)
-
rendermouse
Sep 02, 2021 21:49
example:
var gameInstance = UnityLoader.instantiate("gameContainer", "Build/web.json", { onProgress: UnityProgress, Module: { CachedXMLHttpRequestDisable: true } });
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
- File watcher does not trigger after the AcquireFloatingLease and before the Entitlement check
- HDR Output gets disabled in the Editor when Reflection Probe is enabled during runtime
- The "Build and Run" Menu option tries to build for the selected Build Platform instead of the Active Build Platform
- Font kerning breaks at runtime when multiple UI Documents use different fonts
- MissingReferenceException occurs when entering Play mode with a locked GameObject in the Inspector
Resolution Note:
Starting from Unity 2019, CachedXMLHttpRequest is automatically used for UnityWebRequests (which allows to cache http responses in the indexedDB), unless specified otherwise. In this particular case, the responses are cached, which causes the performance issues.
This issue can be resolved by setting "Module.CachedXMLHttpRequestDisable" instantiate parameter to "true", which should disable CachedXMLHttpRequest for UnityWebRequests