Search Issue Tracker
Duplicate
Votes
0
Found in
2019.2.12f1
2019.4
Issue ID
1302613
Regression
No
[WebGL] "Failed to asychronously prepare wasm: out of memory" error is thrown when loading Player
How to reproduce:
1. Open the attached project's "case_1302613-Project.zip" Scene labeled "Main"
2. Build Addressable Groups (in the Addressables Groups window, Build->New Build->Bash Build High Asset Script)
3. In the Build Settings, switch the Target Platform to WebGL (File->Build Settings)
4. Make a build (name it "BingoWebGL")
5. Host the build on a Mac system
6. Open the built Player in Firefox on Windows
7. Open the Developer Console (shortcut F12)
8. Wait for a few seconds (5-10)
9. Observe the logged messages
Expected result: No errors are thrown
Actual result: "Out of memory" error is thrown
Reproducible with: 2019.4.20f1
Couldn't test with: 2018.4.32f1, 2020.2.5f1, 2021.1.0b7, 2021.2.0a6 (Unresolvable Package errors, obsolete/deprecated errors)
Notes:
- Windows machine must have 4GB of RAM or lower (can also launch a local Windows VM)
- After the build, the index.html file needs to be edited according to the user's description
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
This is a duplicate of issue #1311958