BUG [256-34] Active Picture not releasing memory when destroyed

[AyreGuitar]

Francois, Andos, Yves - I've noticed that when using large images with Active Picture and destroying them repeatedly in the same frame, it can run out of memory very quickly and crash. This is because the memory is not being released properly.
I had emailed this to Francois in May 2012, but I guess it slipped through the net.

To solve the problem (if you don't mind changing stuff in XCode):
In Classes>Extensions>CRunkcpica.m you need to add just 1 line to the destroyRunObject routine:

-(void)destroyRunObject:(BOOL)bFast
{
	[szImageName release];
	if(uConnection != nil)
	{
		[uConnection cancel];
	}
        if(aImage != nil)    [aImage release];   //Add this line to release image data, otherwise can run out of memory quickly and crash your app
}

[Anders]

Thanks, nice find

[Francois]

Ha! Sorry for that.

[Popcorn]

I can confirm that adding that line definately works. My game used to crash the second time the player entered the mainframe, but now it seems to work great! Thanks alot AyreGuitar!