1

Unity mentions in their manual that asset bundles are loaded in Unity WebGL memory heap. They also mention in their blog that dynamic memory size in the heap is not managed (compacted) so fragmentation can occur:

See this image

The image is from Unity official blog and shows the green blocks of fragmented heap memory.

So if we load an asset bundle of say 100mb in the heap and then unload it, that 100 mb will end up as a fragmented block i.e not added to the free memory blocks.

Now if we have N bundles of M size, each load and unload may create a fragmented block and this will cause Unity requiring more and more blocks from the free heap memory. Ultimately at one point, the free heap memory will finish and even though there is a lot of fragmented free space, Unity will not be able to use it and the application will crash.

Is my understanding of this correct?

gman
  • 100,619
  • 31
  • 269
  • 393
Ammar Aslam
  • 43
  • 6
  • I am also working on unity-webgl but i didn't find a proper way to release the memory. Maybe you will find it helpful https://stackoverflow.com/questions/55102548/unity-webgl-asset-bundle-memory-is-not-releasing – Muhammad Faizan Khan Mar 18 '19 at 14:45

0 Answers0