cocos2d for iPhone

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

1. 

   bsharp42
   Member

   I started testing my game on the iphone for the first time and I used Instruments for the first time as well.

   Currently, when I'm sitting on the main menuScene, which is the very first scene when you launch the game, the memory allocated goes up at a low constant rate. Is this normal ?? There isn't any scheduler or any input from the user, but the memory allocated keeps going up....

   Also, what do the blue/red/pink/purple mean ?? I'm guessing red is bad ? lol

   Posted 2 years ago #
2. 

   simo
   Member

   I have been wondering the same thing. I believe moderate memory consumption increase is normal, especially if you've enabled Touches or Accelerometer. The touch events are all objects.
   So far, all of my games have this slow memory build up.

   You might wanna try making a very basic windowed program, and looking at it's memory usage, and comparing the results.

   Posted 2 years ago #
3. 

   crmagicxxx
   Member

   I suppose it's some kind of OpenGL problem reflecting in instruments when tested on device. If you test on simulator you'll see no increasing in allocs. It's not related to touches or anything. Try with cocos 0.8 clean template and you'll also see constant increasing.

   I posted same question maybe a month ago and nobody answered me. If there is some OpenGL expert, maybe he can answer why everything made with cocos has constantly increasing allocations in instruments when tested on device. Though, there are no leaks in code...

   Posted 2 years ago #
4. 

   simo
   Member

   Took a look at this, and it seems the problem is in EAGLView.m and specifically it's swapBuffers method.
   The bottom of the callstack is some Quartzcore function: x_list_prepend_

   Posted 2 years ago #
5. 

   bsharp42
   Member

   Quartzcore function: x_list_prepend_

   Yeap thats one of the things getting called constantly.
   Do you know what that is ?

   Posted 2 years ago #
6. 

   simo
   Member

   I tested Apple's sample project: GLSprite. It has the exact same behaviour: it keeps allocating memory, and the callstack ends with x_list_prepend_

   I'm gonna stop worrying about this "feature" now :)

   Posted 2 years ago #
7. 

   simo
   Member

   This issue was reported in June:
   http://code.google.com/p/cocos2d-iphone/issues/detail?id=391

   edit:
   Also mentioned on Apple Developer forums:
   Graphics and Media Tech. > Open GL ES > Sample GLSprite consumes memory

   The explanation offered is a "known bug in ObjectAlloc".
   So, it's not cocos2d related. The solution is to use Memory Monitor instead.

   The increasing allocs we've been seeing all use the same memory address,
   reserving the same memory over and over again.

   I'm glad I can stop worrying about this.

   Posted 2 years ago #
8. 

   Zemm
   Member

   Thanks for all your research and posting it for the rest of our benefit simo!

   Posted 2 years ago #
9. 

   crmagicxxx
   Member

   Thanks Simo, I feel better now :)

   Posted 2 years ago #

RSS feed for this topic

Reply

You must log in to post.