Sparrow Forum

1. 

   Stylish
   Member

   Hello,

   I have a BIG problem with my memory. Every level I play memory is growing by 10 MB!!! I didn't notice it before because I thought that Allocation instrument were accurate in terms of memory using.

   It's incredible because I don't alloc 10 MB each level.

   Please, I don't know where to start... I need help

   Best regards

   Posted 7 months ago #
2. 

   alex_h
   Moderator

   I would have thought that the only thing that could be causing such a big increase is image data. Try using the debugger or NSLog to make sure that dealloc is really being called on the image content for each level.

   Posted 7 months ago #
3. 

   Stylish
   Member

   What is the best way to draw images?

   SPImage *image = [SPImage imageWithContentsOfFile:@"image.png"];

   or

   SPImage *image = [SPImage alloc] initWithContentsOfFile:@"image.png"];
    
   //..
    
   - (void) dealloc
   {
     [image release];
     [super dealloc];
   }

   I'm using the second way, and maybe not the right way...

   Best regards and thank for your support

   Posted 7 months ago #
4. 

   alex_h
   Moderator

   I also use alloc for images, and then release them once I've added them to the display list. Then when they are removed from the display list they will be dealloced automatically.

   Posted 7 months ago #
5. 

   Jugibur
   Moderator

   The first code snippet uses the autorelease pool, thus will be released automatically after releasing the last created autorelease pool.

   Every app has one autorelease pool by default, created in the main.m file.
   But to release objects created with "autorelease" as soon as possible it's recommended to create and release further autorelease pools, i.e. in the init methods of every object.

   Daniel has created the macro SP_CREATE_POOL(pool) and SP_RELEASE_POOL(pool), so it's not much work to make use of additional autorelease pools.

   So perhaps you check your code for this and test it again.
   And notice: If there is only one more retain as an release, the object stays in memory, though the rest of the level is removed. From time to time I have made such mistakes, but sooner or later have found the culprit.

   Posted 7 months ago #
6. 

   Stylish
   Member

   I found the problem. It's related to a strange behavior of events. I think I would open a new thread because it's a completely different problem and it would help to another user.

   Thanks for your support see you in the next thread!

   Posted 7 months ago #

RSS feed for this topic

Reply

You must log in to post.