memory is higher at the end of the app than when it starts, was just curious what is being stored.
Maybe I forgot to remove an object [import]uid: 79135 topic_id: 15530 reply_id: 315530[/import]
memory is higher at the end of the app than when it starts, was just curious what is being stored.
Maybe I forgot to remove an object [import]uid: 79135 topic_id: 15530 reply_id: 315530[/import]
Maybe not!
I think if you create as an example 100 objects from 100 different images (PNGs) and you remove them, the āhandlesā for the images still exist - as far as I do understand some infos from the docs.
From one point of view this gives advantages - faster loading if you create a second object from the same imageā¦
From another point of view itās bad - an app could open 1000s of images from the web over days and weeks and collect useless informationsā¦
I think the developer should have a grip to handle this - clean the cache as an example [import]uid: 70114 topic_id: 15530 reply_id: 57408[/import]
Are you talking about system memory or texture memory?
You can use this method to see what you have loaded in texture memory.
http://developer.anscamobile.com/code/texture-memory-monitor [import]uid: 67839 topic_id: 15530 reply_id: 57420[/import]
Looks promising. I shall read that now [import]uid: 79135 topic_id: 15530 reply_id: 57421[/import]