Jump to content

Atlas Memory Management


Recommended Posts


In my current project, I stumbled upon a memory problem with the Atlas. Each time we load a State, we load at least 2 Atlas to generate the content of the screen, but I noticed that after the shutdown phase the pixi textures generated for each frame are still in memory.

At first I thought that it was a cache used for loading optimization, but when I return to the same State, the same number of texture are created and added to the cache with the old one created earlier. So each time I get an incrementation of 176 texture in memory resulting in a crash on mobile device.

Is there a proper way to manage the destruction of Atlas or am I missing something?
With this kind of behavior, I cannot relase a stable production on mobile.

Link to comment
Share on other sites


  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...