Search Issue Tracker
Fixed in 5.5.0
Votes
0
Found in
5.4.0f3
Issue ID
829765
Regression
No
Browser Out of memory error when loading asset bundles
-e: Firefox 32-bit ran out of memory with the following error, when loading an asset bundle:
"The browser could not allocate enough memory for the WebGL content. If you are the developer of this content, try allocating less memory to your WebGL build in the WebGL player settings."
-repro:
--IMPORTANT: make sure your default browser is a 32-bit version. Alternatively, after BuildAndRun copy the url from the default browser to, for example, a new tab in Firefox 32-bit.
--build-and-run for webgl
--once loaded in the browser, press Load
--NOTICE you receive an error message (see above)
Note:
- since browsers on OSX are 64-bit. it's easier to repro on Windows
- to reproduce it more than once, you may need to clean the cache, the easiest way is to launch firefox with "-P" parameter, then create a new profile.
- it should be reproducible in 5.3 as well as 5.5 (although 5.5 might crash differently because we removed lzma)
- it should also be reproducible in Chrome
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Duplicate External Textures start appearing when a Texture created with "CreateExternalTexture" is modified causing Memory Usage spikes on VisionOS
- Silent crash when using a "Blend Shape" in a "Skinned Mesh Renderer" to move vertices to Vector3.positiveInfinity, and "Occlusion Culling" is baked
- Some Prefab Source and Override content bounds are misaligned
- The Package Manager's "install packages by..." panels break when Domain Reload is triggered, and the panel is open
- Crash with multiple stack traces when leaving a docked VFX Graph open
Add comment