Ejecta memory management testing

Note that Dominic (the lead dev of Ejecta) identified and fixed a problem that caused WebGL mode in Ejecta to fail to release most textures. If you had problems with memory management in Ejecta before reading this post, try re-downloading the code and testing again: https://github.com/phoboslab/Ejecta

Note that Dominic (the lead dev of Ejecta) identified and fixed a problem that caused WebGL mode in Ejecta to fail to release most textures. If you had problems with memory management in Ejecta before reading this post, try re-downloading the code and testing again: https://github.com/phoboslab/Ejecta

After some testing I can confirm that the fix in Ejecta does the trick and memory offload is happening when changing templates. I monitired also some occasional drop in memory usage while using a layout (playing a game).

This is one of the memory tests I run.

https://dl.dropboxusercontent.com/u/8918895/Screenshot%202014-06-20%2014.38.26.png

hi all,

it seem that is exactly the same if we switch on or off webgl

on simulator and on device connected xcode gives same results with both 2 options

as we can see on the 2 pictures :

1- all images are loaded on start of the game

2 - there is no difference on cpu usage or memory usage

and i used the lastest repo from https://github.com/phoboslab/Ejecta

matrixreal - Ejecta support has been deprecated and is no longer being maintained. We recommend you move to Cordova. See: https://www.scirra.com/blog/154/evolving-construct-2s-export-options