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
- Highlighter.Highlight does not find window when using class name as window title
- Highlighter.Highlight highlights a different component when multiple components have the same property path
- Highlighter.Highlight does not find elements in an array or list when the array or list is collapsed
- [URP][NRP] RenderPass, BeginSubPass, and EndRenderPass errors are thrown when Native RenderPass is enabled
- D3D11 swapchain error pop-up appears and the Editor shuts down when Generating Lighting with Probe Volumes present
This is a duplicate of issue #1311958