Strange (due to ignorance) crash when setting kTexture2DPixelFormat

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

Strange (due to ignorance) crash when setting kTexture2DPixelFormat_RGBA4444

(11 posts) (5 voices)

Started 1 year ago by matsebc
Latest reply from matsebc

Tags:

No tags yet.

matsebc
Member
Ok I am making this game in whicih I load a bunch of textures from memory, so far I have been using kTexture2DPixelFormat_RGBA8888 and everything worked fine (except on 1st gen devices) in which the memory at load time was way too excesive and caused a crash. In any case I tried setting my texture mode to kTexture2DPixelFormat_RGBA4444 and the application crashes as soon as it tries to load the first texture, I don't really know what could be going on but here is the the debugger output of the crash, if anyone has any tips, I will be very thankful for it.
By the way all my images are .png.

I setup the director as follows
```
if( ! [CCDirector setDirectorType:CCDirectorTypeDisplayLink] ) {
		[CCDirector setDirectorType:CCDirectorTypeDefault];
	}

	self.cocosView = [[UIView alloc]initWithFrame:CGRectMake(0, 0, 100, 100)];
	[self.window addSubview:self.cocosView];
	// Use RGBA_8888 buffers
	// Default is: RGB_565 buffers
	[[CCDirector sharedDirector] setPixelFormat:kPixelFormatRGBA8888];

	// Default texture format for PNG/BMP/TIFF/JPEG/GIF images
	// It can be RGBA8888, RGBA4444, RGB5_A1, RGB565
	// You can change anytime.
	[CCTexture2D setDefaultAlphaPixelFormat:kTexture2DPixelFormat_RGBA4444];

	[[CCDirector sharedDirector] setProjection:CCDirectorProjection3D];
	[[CCDirector sharedDirector] setDepthBufferFormat:kDepthBuffer24];
	[[CCDirector sharedDirector] setDepthTest:YES];

	[[CCDirector sharedDirector] attachInView:self.cocosView];
```
And it crashes when loading the first texture.
I am attaching an image of the crash.

wanted to add:
Cocos version : cocos2d: cocos2d v0.99.1-pre

More info:
crash stack trace
#0 0x036875cc in twiddle32x32_rgba16_4444 ()
#1 0x0368813c in ARMTwiddleRGBA16_4444 ()
#2 0x0360f0be in gldModifyTexSubImage ()
#3 0x034b8712 in glTexImage2D_Exec ()
#4 0x30fe90a6 in glTexImage2D ()
#5 0x000fcb58 in -[CCTexture2D initWithData:pixelFormat:pixelsWide:pixelsHigh:contentSize:] (self=0x5778550, _cmd=0x14486c, data=0x59ab000, pixelFormat=kTexture2DPixelFormat_RGBA4444, width=1024, height=512, size={width = 576, height = 512}) at /Users/matsebc/Desktop/Applications/Elance/xodo/ManaRealms/Mana Realms/libs/cocos2d/CCTexture2D.m:127
#6 0x000fe67c in -[CCTexture2D(Image) initRGBATextureWithImage:pixelsWide:pixelsHigh:] (self=0x5778550, _cmd=0x14ade4, CGImage=0x577f330, POTWide=1024, POTHigh=512) at /Users/matsebc/Desktop/Applications/Elance/xodo/ManaRealms/Mana Realms/libs/cocos2d/CCTexture2D.m:493
#7 0x000fd518 in -[CCTexture2D(Image) initWithImage:] (self=0x5778550, _cmd=0x334bf894, uiImage=0x58b3cc0) at /Users/matsebc/Desktop/Applications/Elance/xodo/ManaRealms/Mana Realms/libs/cocos2d/CCTexture2D.m:208
#8 0x00102a44 in -[CCTextureCache addImage:] (self=0x302710, _cmd=0x334dd670, path=0x54c6e30) at /Users/matsebc/Desktop/Applications/Elance/xodo/ManaRealms/Mana Realms/libs/cocos2d/CCTextureCache.m:186
#9 0x000f9804 in -[CCSpriteSheet initWithFile:capacity:] (self=0x58b3f50, _cmd=0x13d324, fileImage=0x54c6e30, capacity=29) at /Users/matsebc/Desktop/Applications/Elance/xodo/ManaRealms/Mana Realms/libs/cocos2d/CCSpriteSheet.m:92
#10 0x0007b9e8 in -[MRSpriteSet initWithFile:width:height:dye:] (self=0x58b3f50, _cmd=0x13d26c, source=0x54c6e30, aWidth=64, aHeight=64, d=0x0) at /Users/matsebc/Desktop/Applications/Elance/xodo/ManaRealms/Mana Realms/Classes/MRSpriteSet.m:19
#11 0x0007b950 in +[MRSpriteSet spriteSetWithFile:width:height:dye:] (self=0x155a00, _cmd=0x13d1c0, source=0x54c6e30, aWidth=64, aHeight=64, d=0x0) at /Users/matsebc/Desktop/Applications/Elance/xodo/ManaRealms/Mana Realms/Classes/MRSpriteSet.m:15
#12 0x00078f5c in -[MRAnimatedSpriteConfiguration loadSpriteSetFromNode:palette:] (self=0x586a4a0, _cmd=0x13d038, child=0x586a750, palette=0x0) at /Users/matsebc/Desktop/Applications/Elance/xodo/ManaRealms/Mana Realms/Classes/MRAnimatedSpriteConfiguration.m:157
#13 0x000789ac in -[MRAnimatedSpriteConfiguration loadSpriteFromXmlNode:variant:palette:] (self=0x586a4a0, _cmd=0x13d078, node=0x5767840, variant=0, palette=0x0) at /Users/matsebc/Desktop/Applications/Elance/xodo/ManaRealms/Mana Realms/Classes/MRAnimatedSpriteConfiguration.m:112
#14 0x00078624 in -[MRAnimatedSpriteConfiguration initWithDDXMLElement:variant:palette:] (self=0x586a4a0, _cmd=0x13d0a0, root=0x5767840, variant=0, spritePalette=0x0) at /Users/matsebc/Desktop/Applications/Elance/xodo/ManaRealms/Mana Realms/Classes/MRAnimatedSpriteConfiguration.m:90
#15 0x00078390 in +[MRAnimatedSpriteConfiguration loadConfigurationFromFile:variant:] (self=0x1559d8, _cmd=0x13cbec, file=0x5868450, variant=0) at /Users/matsebc/Desktop/Applications/Elance/xodo/ManaRealms/Mana Realms/Classes/MRAnimatedSpriteConfiguration.m:76
#16 0x000784a4 in +[MRAnimatedSpriteConfiguration loadConfigurationFromFile:] (self=0x1559d8, _cmd=0x13ab1c, path=0x5868450) at /Users/matsebc/Desktop/Applications/Elance/xodo/ManaRealms/Mana Realms/Classes/MRAnimatedSpriteConfiguration.m:81
#17 0x00063bf8 in -[MRPlayer setSpriteWithId:inSlot:ofColor:] (self=0x54d3070, _cmd=0x12f9b4, sId=0x5868f20, slot=0, color=0x151b00) at /Users/matsebc/Desktop/Applications/Elance/xodo/ManaRealms/Mana Realms/Classes/MRPlayer.m:125

(BTW all that is in a brand new project I created just to test).

Ok even more info this is one of the files that works great when using 8888 but crashes when using 4444.

This other one

looks like this when using 4444.
Posted 1 year ago #
Karl
Member

These kinds of bugs are usually caused by memory corruption, due to some other code walking all over your memory.

Your best bet is to try loading the texture in a completely separate project that has none of your custom code, and then work back from there.

You can also try using NSZombieEnabled to see if it's accessing a released object:
http://www.cocoadev.com/index.pl?NSZombieEnabled

Posted 1 year ago #
matsebc
Member

@Karl this happens in a project I created specificaly to test this issue with cocos2d, all it does is create a scene node, create a CCSprite and add it to the scene, so in this case I doubt it is somethign else stepping on my memory, thanks for the suggestion though.

Posted 1 year ago #
Karl
Member

Ok, sorry. I had assumed that the stack trace you'd posted was from the test app.

Another thing you might try is opening and saving the PNG files with a different program than the one you are using. I've had PNGs that my artist gave me do weird things in iPhone even though they displayed fine in Preview. But opening and saving them in gimp seemed to fix the issue when it cropped up.

Actually, looking at the screenshot again, the FPS display is garbled too. Can you post the test program in its entirety, including the scene and layer? You might have hit on a bug. Does the FPS display get screwed up even if you don't load any textures?

Posted 1 year ago #
matsebc
Member

Yes you are right, the stacktrace os of the actual application but on the test project exactly the same error occurs, I will post the entire porject once I get home, also will look if the numbers pmg looks scrambled as well.
I already tried resaving the png, with Photoshop not gimp though, will try that as well, tried resaving as png24 and png8 same issue in both cases

Posted 1 year ago #
matsebc
Member

Here is the project, when only showing the FPS it shows scrambled so now I am leaning towards a bug on cocos2d.
Was going to remove the libraries folder but left it all just in case.

Apologies about the hosting but I do not currently own one to upload the file to.

http://www.mediafire.com/?mnfxe2idunm

The project is just the default cocos template with a few lines that add a scene and a sprite (forgot to uncomment some lines which I commented to test if only the numbers looked scrambled), included the other images I was trying to load as well.

Hope this sheds some light on the issue.

Posted 1 year ago #
InsertWittyName
Member

The problem is that the code in CCTexture2D.m doesn't allocate power-of-two sizes when it's altering the pixel format of the texture.

Allocating POT sizes stops the crashing, but the bit twiddling code also needs updating to rectify this.

I'd raise a ticket for a bug.

Posted 1 year ago #
InsertWittyName
Member

Created an issue with the patch http://code.google.com/p/cocos2d-iphone/issues/detail?id=813&sort=-id&colspec=ID%20Type%20Status%20Priority%20Milestone%20Component%20Owner%20Summary

Posted 1 year ago #
riq
Key Master

@InsertWittyName: Thanks for the patch.

@matsebc: v0.99.1-rc works fine. It seems that you are using a version between v0.99.0 and v0.99.1-rc

Posted 1 year ago #
abitofcode
Moderator

@matsebc Have you looked at dropbox https://www.dropbox.com/ I use it to pass work back and forth to Mike (designer). There is a public folder as well as privately shared ones. Between this and skype we've not had to meet up now for 6 months while working on STAPig.

Best bit is it works nicely between PC and Mac! All you then need is git or subversion and you're probably running more efficiently than most commercial media companies ;)

Posted 1 year ago #
matsebc
Member

@riq thanks! apologies about that.
@abitofcode awesome info, i'll take a look at it right away!.

Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.