Out of Memory when i use 480x320 texture as background, Pls Help: going crazy!

cocos2d for iPhone » Programming » cocos2d support (graphics engine)

Out of Memory when i use 480x320 texture as background, Pls Help: going crazy!

(16 posts) (4 voices)

Started 1 year ago by ops8086
Latest reply from ops8086

Tags:

ops8086
Member

Hi, i'm using cocos2d on my game, which consists of many scenes that changes very often (it is a quiz game, and every quiz "question" is a scene, so i replaceScene in the directory every time the user answer a question.

In my scene class, in the init, i set the background image (the same for all questions):

backgroundLayer = [CCLayer node];
[self addChild: backgroundLayer];

bg01 = [CCSprite spriteWithFile:@"background_03.png"];
bg01.position = ccp(240,160);
[backgroundLayer addChild: bg01];

THE PROBLEM: the game goes Out of memory soon when i play a little, and analyzing the memory usage with Instruments Xcode tool i see that every time i replace the scene with another one the memory used by the game increases by about 1 MB !!. I saw for memory leaks, but i cannot find any made by me.

I also tried to comment the three lines about which load the background sprite and adds to the backgroundLayer, and without this the memory increases in each scene is very few (only about 150-200 kb per scene).

So it seems that for some reason that background image is loaded in memory but it is not freed, i also tried to call [[CCTextureCache sharedTextureCache] removeAllTextures] on the OnExit of each Scene, but this doesn't help to free memory.

Using Cocos2D 0.99.4, trying on iPad (even if it is an iPhone game, but i've no iphone actually).

Any ideas ?
Please help me, i'm going crazy....! :)

Thank you very much!

Posted 1 year ago #
riq
Key Master

Try these tips:
http://www.cocos2d-iphone.org/wiki/doku.php/prog_guide:best_practices#reducing_memory

Posted 1 year ago #
ops8086
Member

Thanks Riq, i already read that tips, and i call removeAllTexture on each scene in the OnExit method, so it should free the memory occupied by the background image and i should have about the same occupied memory in each scene... instead the occupied memory increases by 1 mb in each scene (so in each questions) and it drains all the device memory in few questions and then go out of memory.

I can't find where is the problem.

Posted 1 year ago #
riq
Key Master

You might have a memory leak, but if you don't you should reduce memory by using low-res textures (16-bit or 4-bit textures).
The link that I posted shows how to use lower-res images.

Posted 1 year ago #
chrisco
Member

Can you the post the code for one full scene? What you're doing now sounds correct (though I removeUnusedTextures in my -dealloc method) so it's hard to tell what the problem might be...

Posted 1 year ago #
ops8086
Member

If i only do [Sprite spriteWithFile... and addChild to a layer i shouldn't have memory leaks, even if i don't release these object, it's right ?

And when i use spriteWithFile the image is loaded in the shared texture cache ? so if i do removeAllTextures it should be freed in all cases (with memory leaks and with no memory leaks), is this right ?

Posted 1 year ago #
ops8086
Member

I would show you the code, but it is long... each scene class is derived from 2 base classes (which does the most work) which is then derived from CCLayer.

Also, in the final derived scene, i make a static method +scene because i saw that in the cocos template it use to do that.... is this correctly to have the scene statical method only in the final derived scene class ? and then call [classname scene] instead of [classname node] when i do replaceScene in the director ?

Posted 1 year ago #
Mark Sawicki
Member

@ops8086,

Do you see your dealloc getting called for that scene when you switch to the next scene?

-Mark

Posted 1 year ago #
ops8086
Member

yes it's called.... this is a very strange thing.

Posted 1 year ago #
ops8086
Member

I'm uploading some source code on my webserver, and i'll post you the link, if some of you could take a look and help me i would appreciate it :) Thanks

Posted 1 year ago #
ops8086
Member

Ok, here is some source code:

http://www.marcosiino.it/code.zip

Q01_Step001 is the first question scene, Q01_Step002 is the second and so on. Each of these classes derives from BaseSequenceQuestions which derives from BaseScreen which derives from CCLayer.

Main is the first menu screen which launches Q01_Step001.

Basically the BasicScreen takes care of common scene elements, like touches handling and detection of which sprite has been touched, and other things... it also initialize the background image (the one i think that give the memory problem, in the init method) and add it to the backgroundLayer.

The BasicSequenceQuestion class allows to set a sequence of sprite you've to touch to answer correctly to the question. For example a question might ask "press blue, red and yellow", with a scene derived from BasicSequenceQuestion is easy to add the blue, red and yellow sprite to the "correct" sequence, and when the user touch the correct sequence it automatically pass to the next scene.

As i said, i think the problem is in the background image because if i comment it the memory occupied in each scene doesn't has big increases. Instead with the background image for each scene (question) the occupied memory increases by a lot (about 1 MB), so *i think* the problem is there.

Hope you can help me, Thank you very much.

Posted 1 year ago #
ops8086
Member

Oh, just for info: i'm actually set the director to use 16 bit textures (if i use 32 bit textures the increases in memory for each scene is about double). The background image is a 480x320 png.

Posted 1 year ago #
chrisco
Member

I just took a quick glance, but see that you're not calling [super dealloc] in your BaseScreen.m file. Can you add that in and test to see if it fixes anything?

Posted 1 year ago #
ops8086
Member

Oh my god! it is 2-3 days i'm going crazy with this and i didn't realize that was missing the [super dealloc]!!!!

I'm trying it now and it seems to work now...the occupied memory is mantained about the same in all the scenes now and sometimes it also decreases!

the most stupid things is the one that need more time to find out! :)

THANK YOU VERY VERY VERY MUCH!!!!! :)

Posted 1 year ago #
chrisco
Member

So does that mean I don't have to go through the rest of your code? ;)

Glad that worked for you!

Posted 1 year ago #
ops8086
Member

Yes, it works :) thank you very much :D the fun thing is that i saw all the dealloc methods, onEnter, onExit, etc... of every classes to see if i call the super method, but i didn't realized that in the dealloc of BaseScreen it was missing :)

You saved me a lot of time :)

Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.