cocos2d for iPhone

A fast, easy to use, free, and community supported 2D game engine

1. 

   pabloruiz55
   Member

   Hi!
   On init of my scene i am loading 3 spritemanagers each with a 1024 * 1024 png texture.

   backMgr = [AtlasSpriteManager spriteManagerWithFile:@"backs.png" capacity:50];
   [self addChild:backMgr z:1 tag:kBackTagAtlasSpriteManager];

   during this operation the object allocation rises up to 30 mb. then after it finishes loading it goes down to a reasonable amount.

   The thing is that many times it would crash from memory problems.

   It looks like that as soon as the init method is finished the memory is released. I tried loading an image, scheduling for some seconds later the load of another one, but the memory keeps rising, as long as the step methos is not scheduled and the init finished the memory allocation does not drop.

   Posted 2 years ago #
2. 

   pabloruiz55
   Member

   One weird thing is that if i finish the game, exit to the main menu (another scene) and then play again, memory allocation does not rise to 30 mb like the first time...
   Any ideas?

   Posted 2 years ago #
3. 

   pabloruiz55
   Member

   I haven't been able to solve this problem yet...
   More info, maybe a wasn't clear before...

   On init of the scene i am initializing my clases, atlasspritemanagers,etc.
   During this, the object allocation rises to 30 MB, after this is done i schedule my gameloop.
   As soon as the gameloop starts running the object allocation drops to 4MB.

   I have tried separating the loading load an spritemanager, wait sometime, load another one,etc. But the mem allocation still rises to 30.

   How could i make it so this doesn't happen? I am loading 4 atlasspritemanagers so if i am not wrong i am allocating around 4MB for each texture (?) and apparently it is happening at the same time or something.

   What i see in instruments if i initializae a manager , then schedule for loading another one after sometime; is that allocation rises to lets say 8mb (it never goes down) then it rises to 16 (the other manager is being initialized) and then when the init (or onEnter - the same happens- ) is finished object allocation goes down to 4-5MB

   Posted 2 years ago #
4. 

   pabloruiz55
   Member

   Well, after some work i figured this out.
   If i use the manager inmediately after creating it the memory allocation does drop.

   If i instantiate one atlasspritemanager after another memory allocation incresases like 8mb to 16mb to 24mb.

   But if i instatiate one, use it to create at least an atlas sprite, then instantiate the other and so on, memory allocation increases like 0mb to 8mb, then 8mb to less than 1mb then 1mb to 9mb and so on.

   Could this be a bug? Is there a correct solution for solving this other than doing what i did?

   Right now i solved it by creating the manager and using it after that. Just writing it here for future reference.

   Posted 2 years ago #
5. 

   Steve Oldmeadow
   Administrator

   What device/OS combinations did this occur on?

   Posted 2 years ago #

RSS feed for this topic

Reply

You must log in to post.