"check_safe_call: could not restore current frame" error on device?

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

"check_safe_call: could not restore current frame" error on device?

(8 posts) (7 voices)

Started 2 years ago by malphigian
Latest reply from Lonzz

Tags:

check_safe_call crash replaceScene

malphigian
Member

I'm uncertain if this is related to Cocos2d or something else I am doing wrong, but I'm not even sure how to diagnose the problem.

My game works perfectly in the simulator. I've done a lot of testing for memory leaks and there don't seem to be any (as far as I can tell as an amateur with Instruments).

My game is made up of a series of minigames each with their own scene. When I run the game on my device (3.0) the game crashes after a few scenes (anywhere from 2 to 5). It's not any particular scene, but it always crashes after the next scene init is called but before the replaceScene transition runs. The error it crashes with is this:
--
Program received signal: “0”.
warning: check_safe_call: could not restore current frame
--

Nothing else. I tried enabled NSZombieEnabled, but still received the same error.

Again, it never crashes in the simulator and will run through dozens of scenes with no complaint.

I know it's hard to diagnose this sort of thing without code, but does anyone have any tips for what might be causing this error? My google searches are turning up nothing useful.

Thanks in advance!

Posted 2 years ago #
crmagicxxx
Member

My guess is that you're not retaining something you should. There are differences in simulator and device, maybe on simulator something is kept longer in memory thus you don't see any problems. And when tested on device, it's released sooner so you get crash.

I had exact problem once with Chipmunk, freeing shape with Sprite in it, and never saw problem in simulator until I tested on device. Or vice-versa, I can't remember now.

Something else just came to me. Do you maybe try to go to next scene automatically inside the init method of the previous one? If so, then try to schedule method even with tiny interval like 0.1 seconds and in that method call replaceScene. I had same problem with my IntroScene, which does nothing except displaying Default.png image and going to next scene with transition automatically.

Posted 2 years ago #
malphigian
Member

Thanks for the advice crmagicxxx.

I pinpointed the problem to a bit of stupidity on my part. For some reason I was doing this in the dealloc of each scene:
[[TextureMgr sharedTextureMgr] removeAllTextures];

Why would I unload all my textures, even though I was in the middle of reusing many of them? I have no idea why, I think I was testing something at some point and forgot to remove that line.

Anyway, the iPhone did not like me taking all the textures away that frequently.

Posted 2 years ago #
youke
Member

The question has been decided????

Posted 2 years ago #
teedr
Member

Wow...this is why this forum is so awesome.

Anyway, just wanted to say for future readers that I had the same problem.
It seems that if you are removing too many textures very frequently you'll get this issue.
At least that was what happened in my case.

Posted 2 years ago #
smcguffee
Member

I have the same problem and can't find any solution anywhere. Does anyone have a solution or any information regarding programs randomly exiting and spitting out:

Program received signal: “0”.
warning: check_safe_call: could not restore current frame

Posted 1 year ago #
adik
Member

I think it might be because you are running out of memory. Check your iPhone crash logs.

Posted 1 year ago #
Lonzz
Member

Had the same issue. After a day of searching I found the problem. Stupid error from my side:

After a change in code I wanted to use CCCallFuncN instead of CCCallFuncND but declared it still as CCCallFuncND but with the parameters of CCCallFuncN.

Wrong:

CCCallFuncND* oloIsOut = [CCCallFuncND actionWithTarget:self selector:@selector(onHidden:)];

Right:

CCCallFuncN* oloIsOut = [CCCallFuncN actionWithTarget:self selector:@selector(onHidden:)];

Maybe it helps anyone...

Posted 2 months ago #

RSS feed for this topic

Reply

You must log in to post.