CODEWITHSUNDEEP
iphoneiosmemorycocos2d-iphonememory-leaks
user1082068
user1082068

Reputation: 53

cocos2d using gobs of memory

I'm having the absolute worst time with running out of memory in my game with cocos2d.

I have 4 scenes. two vanish from memory when I switch scenes using 

[[CCDirector sharedDirector]replaceScene:sceneWithTransition]

I've tried push/pop and it makes the problem about 10x worse.

2 of the scenes however are like a virus. The conditions under which I can remove them from memory do not exist. I am using the ARC alterations. I was hoping they would help, they did not.

I've overridden the cleanup method to make sure I get rid of references to everything in the scenes. The first one is the game play scene, and I can imagine how it might be possible that I've missed something that is somehow holding on to the scene. However the other one is the settings scene. It has 5 parts. they all get tossed and yet the scene will not purge. before converting to ARC the app was unusable it crashed so often and when it wasn't crashing it was running out of memory. After ARC it lasts about 4x longer than before but still runs out of memory regularly. Crashes however are almost non-existant.

I suppose first off, what is the correct way to switch between scenes? Second, how does one remove something from memory when using arch because object = nil does nothing. All of my other programs using ARC run like dreams. None of them use the cocos2d engine. I'd not seen a memory error since the introduction of arc until I made the mistake of converting my quartz2d game in to cocos2d. The only reason I don't o back to a platform that actually functions is that I really like the effects possible in cocos that I simply cannot make work in quartz.

Upvotes: 0

Views: 225

Answers (2)

johnbakers
johnbakers

Reputation: 24771

push/pop from what I understand use a "stack" model thus memory is not erased when new scenes are pushed or popped, which would explain why that gets worse when using this method.

one way you can help save memory, especially during a transition, is to transition to a loading scene and then from there transition to the actual scene you want. This is because during a normal transition, both scenes occupy memory simultaneously for at least 1 frame, whereas a cheap loading scene will instead take each of their places, reducing the horrible memory spike that often occurs when transitioning between two intense scenes.

Upvotes: 1

sergio
sergio

Reputation: 69047

It seems that cocos2d had some issues with ARC that got fixed only recently.

I don't know if this has to do with your memory problems, but you might check which cocos2d version you are using.

Anyway, it seems that cocos2d will fully support ARC only from version 2.0. So, you might be better off not using ARC and getting your memory management right by properly using release. As far as I know, cocos2d has no memory problem, so you should be able to accomplish it.

Upvotes: 1

Related Questions