Memory warning causing spritesheet to be recreated, resulting in NSAssert

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

Memory warning causing spritesheet to be recreated, resulting in NSAssert

(6 posts) (2 voices)

Started 1 year ago by Bongeh
Latest reply from Bongeh

Tags:

Bongeh
Member

I've got a problem where I am creating my sprites.

If I get Received memory warning. Level=1 the next sprite that is created incorrectly points to a new spritesheet. Resulting in *** Assertion failure in -[CCSpriteBatchNode addChild:z:tag:], .../libs/cocos2d/CCSpriteBatchNode.m:202

I have 2 spritesheets, this error happens as I pass from my Menu into my Game.

The menu and the game have 2 seperate spritesheets (both 1024x1024 in size), the gameScene loads a Box2d world, so at the point of the game loading, there are 2 full spritesheets and a box2d world in existence, would this be enough to cause a memory issue?

I'm looking for ways to a) protect the spritesheets from being recreated after a memory warning or b) ideas on how to prevent the memory warning in the first place.

Thanks

Posted 1 year ago #
TBBle
Moderator

If this is an iOS 4 device, I'd suggest setting a flag during the transition, and ignoring the memory warning while the flag's set.. A level1 memory warning's only a warning, after all. You'll get a level 2 before you're a candidate to be killed out-of-hand. And in theory any background tasks should be getting out of your way at this point anyway.

Posted 1 year ago #
Bongeh
Member

I'm developing on an iPhone 3G, in theory, if i get 50-60fps on this, everyone who plays my game will be happy! :)

I tried retaining the spritesheet, it still seems to change.

Whats odd, is that the memory warning only shows up once every 3-4/10 times the game is run..

Posted 1 year ago #
Bongeh
Member

Hmm thought't i'd managed to fix it, but seemingly not.

I'm going to try a loading transition scene that has very little resources within it, so i can move to that, completely remove the main menu, and then load in the game scene.

It's a shame because it might add a few seconds onto the users wait for the game to load, but it guess its better that than random crashes!

Posted 1 year ago #
Bongeh
Member

Seems to have fixed it.. just need to remember how to get a sprite to animate on a seperate thread so that the 'loading' animation doesn't stutter.

Posted 1 year ago #

Tried to load the gameScene on another thread, but now im having issues with NSLock, presumably my spritesheets are being accessed across multiple threads.

Received memory warning. Level=1
*** -[NSLock dealloc]: lock (<NSLock: 0x3ded70> '(null)') deallocated while still in use
 *** Break on _NSLockError() to debug.
 *** -[CFDictionary setObject:forKey:]: message sent to deallocated instance 0x3decc0

How can I isolate a singular sprite so that it's animation is never interupted by other things loading? Any ideas?

Note: I am adding my gamescene as follows

button with this code

	NSThread* thread = [[[NSThread alloc] initWithTarget:self selector:@selector(goToNextScene) object:nil] autorelease];
	[thread start];

-(void) goToNextScene {

	NSAutoreleasePool *autoreleasepool = [[NSAutoreleasePool alloc] init];

	EAGLContext *k_context = [[[EAGLContext alloc]
							   initWithAPI :kEAGLRenderingAPIOpenGLES1
							   sharegroup:[[[[CCDirector sharedDirector] openGLView] context] sharegroup]] autorelease];
	[EAGLContext setCurrentContext:k_context];

	CCScene *gs = [GameEngine scene];

	[[CCDirector sharedDirector] replaceScene:[CCTransitionFade transitionWithDuration:0.5 scene:gs]];

	[autoreleasepool release];

}

This code works on a previous game that is live on the app store, but I was only using one singular sprite sheet, so the memory used was alot less, i think what's happening is as the gameScene is loaded (containing 2 spritesheets), it is causing the memory warning which is perhaps killing the NSLock.

Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.