Sparrow Forum

1. 

   enbr
   Moderator

   http://cl.ly/3s1B2G3M0i0C2k0G2o3D
   What am I doing wrong?

   I think it is a result of this code. I am making three buttons like this.

   playButton = [SPButton buttonWithUpState:[SPTexture textureWithContentsOfFile:@"menuchiligreen.png"] text:@"Play"];
   playButton.fontName = @"Blazed";
   playButton.fontSize = 35;
   playButton.fontColor = 0xD9A031;
   playButton.textBounds = [SPRectangle rectangleWithX:playButton.textBounds.x y:playButton.textBounds.y+5 width:playButton.textBounds.width height:playButton.textBounds.height];
   playButton.x = 320/2-playButton.width/2;
   playButton.y = 100;
   [playButton addEventListener:@selector(playButtonTriggered:) atObject:self forType:SP_EVENT_TYPE_TRIGGERED];
   [menu addChild:playButton];

   Posted 1 year ago #
2. 

   baike
   Moderator

   I think that's just Daniel pooling some rectangles for future use. I wouldn't worry about it unless you see them starting to leak excessive amounts of memory. I considered it a false positive.

   Posted 1 year ago #
3. 

   enbr
   Moderator

   Ok thanks. I don't need them in the future. Can I release them somehow?

   Posted 1 year ago #
4. 

   Daniel
   Primary Feather

   Yes, the reason for the leak could be that Sparrow is pooling objects that are needed often, that is: rectangles, points and matrices.

   Thus, even if you don't need those objects, Sparrow might recycle them in its render methods.

   You can disable pooling completely by defining the following preprocessor macro (in the project's build settings):

   DISABLE_MEMORY_POOLING

   I wouldn't recommend to do so, though -- you'll lose some performance and gain little memory. (And as soon as memory gets critical, Sparrow purges its pools automatically, anyway.)

   Posted 1 year ago #
5. 

   enbr
   Moderator

   Thanks

   Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.