There we go logical error... It's good that you fixed it.

fixed... I had sprite as a property with (readwrite,retain), stupid me.... I even looked right at it a couple of times last night and it didn't even register until this morning... I guess that's what sleep can do for you!

I wondered about that... my code does assume that parent is ccAtlasSpriteManager... but the removal does stop it from displaying so that must be right.... right?

I tried checking the retain counts but they seemed all whack. I read somewhere that you shouldn't count on those because there's a lot of things you don't expect that happens with NSObjects during their life.

I'm going to see about confirming that parent... [edit] confirmed, they are the same parent obj...

ok, that makes me feel better... the only other code is stuff just moving the sprite around and some actions. those all dealloc as they are supposed to with the call to removeChild. In the code above, sprite is a weak reference but that's really it. I'm pretty sure that if I keep the release in there I will eventually start getting errors because of over release...

my project is still running under the 8.2 beta... maybe there was a leak. is there any easy way to update the cocos framework in an existing project?

Perhaps since you are calling the removal from itself.parent?

You can always nslog out the current retainCount before calling this to see for sure.

Your thinking is correct. Is the sprite never being deallocated at a really later time?

It could be some logical error you made before or there is a bug in cocos. The snippet of code is too little to really verify anything though.

I'm a bit confused... if I do:

AtlasSprite * sprite = [AtlasSprite spriteWithRect:allFrames[index].rect spriteManager:ccAtlasSpriteManager];
[ccAtlasSpriteManager addChild:sprite];

I then think the sprite should be dealloc'd after this:
[sprite.parent removeChild:e.sprite cleanup:YES];

My thinking for that is because addChild retains the obj so shouldn't removeChild release? Now, the removeChild does remove it from being drawn but I have to do a [sprite release] to actually get it to dealloc. If I only do that and not the release then the object continues to be displayed.

I expect to not have to release since I'm using an AtlasSprite convenience constructor. what am I doing wrong here?