Switching Views throws a "EXC_BAD_ACCESS".

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

Switching Views throws a "EXC_BAD_ACCESS".

(16 posts) (5 voices)

Started 1 year ago by Pedagogic368
Latest reply from Pedagogic368

Tags:

Pedagogic368
Member

Hello I am getting the dreaded "EXC_BAD_ACCESS" when attempting to switch to a EAGLView -
I understand from what I have read on the forum that I might be "retaining" an object incorrectly - but I am not sure how to find this. Any suggestions would be greatly appreciated.

From my console -

run
Running…
[Switching to thread 12035]
[Switching to thread 12035]
sharedlibrary apply-load-rules all
continue
2010-08-10 12:35:38.514 cocos2dXrefTest[13501:207] Received memory warning. Level=1
Program received signal: “EXC_BAD_ACCESS”.
(gdb)

My code is as follows:

- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
	// Init the view

	newView = [[UIView alloc] initWithFrame:[[UIView mainScreen] bounds]];

	// must be called before any other call to the director
	if( ! [CCDirector setDirectorType:kCCDirectorTypeDisplayLink] )
		[CCDirector setDirectorType:kCCDirectorTypeThreadMainLoop];

	CCDirector *director = [CCDirector sharedDirector];

	// set FPS at 60
	[director setAnimationInterval:1.0/60];

	// Display FPS: yes
	[director setDisplayFPS:YES];

	// before creating any layer, set the landscape mode
	[director setDeviceOrientation:kCCDeviceOrientationLandscapeLeft];

	// Create an EAGLView with a RGB8 color buffer, and a depth buffer of 24-bits
	EAGLView *glView = [EAGLView viewWithFrame:[newView bounds]]; 

	[director setOpenGLView:glView];

	// High res mode
	//	[director setContentScaleFactor:2];

	[glView setMultipleTouchEnabled:YES];

	CCScene *scene = [CCScene node];

	[scene addChild: [LayerExample node]];

	[director runWithScene:scene];

	return YES;

}

Posted 1 year ago #

lordbritishix
Member

you can try using NSZombies to debug EXC_BAD_ACCESS problems:
http://www.codza.com/how-to-debug-exc_bad_access-on-iphone

Posted 1 year ago #
Pedagogic368
Member

Hi, I read online how to run the NSZombies to debug, check marked it and got the following information in my console - How do I read and apply these results? Thanks

run
Running…
[Switching to thread 12035]
[Switching to thread 12035]
sharedlibrary apply-load-rules all
continue
2010-08-10 12:35:38.514 cocos2dXrefTest[13501:207] Received memory warning. Level=1
Program received signal: “EXC_BAD_ACCESS”.
(gdb)

Posted 1 year ago #
Mark Sawicki
Member

@Pedagogic368,

Right after it crashes, at the gdb prompt, type in 'bt' and you should see a back trace of the last things executed before the crash.

(I'm working on my own little bugger right now ;) )
-Mark

Posted 1 year ago #
Pedagogic368
Member

Thanks Mark- I am actually able to get the scene up (First time !!!) I am now receiving a EXC_BAD_ACCESS at the

CCDisplayLinkDirector preMainLoop
[self drawScene];

is there documentation on what to do or how to handle all these different EXC_BAD_ACCESS results? I have a list of them - funny thing is that I am using code from the coco2ds website on how to set an EAGLView using IB - not sure why all these come up?

Thanks Linda

Posted 1 year ago #
Mark Sawicki
Member

@Pedagogic368,

Hmm, not sure I can directly be of much help with this. I take the easy way out and just use the cocos view macro( CC_DIRECTOR_INIT() ), and don't have a need to create other views.

Are you sure you set up the NSZombieEnabled property correctly?
Also, there may be something in here that could help you in finding those bugs(they are useful to me anyway..), especially the part about 'Breaking on Exceptions ' Debugging Techniques

-Mark

Posted 1 year ago #
Pedagogic368
Member

Thanks Mark - I will review them - Guess I should be happy that I got the IB with the EAGlView up finally!! Small steps - I am getting there..BTW is there a place I can go to acquire about and request PAID COCO2ds help? I would really like to know how t set this type of thing up. Thanks.

Posted 1 year ago #
Mark Sawicki
Member

@Pedagogic368,

I'm not sure about the paid cocos2d-iphone development, but for my own learning when I was getting started, it really was all about the samples/test included in the framework download, AND I got a huge jumpstart by getting the Sapus Tongue Source. I am not ashamed to admit it! heh.

-Mark

Posted 1 year ago #
Kitsune
Member
@Pedagogic368,

Not sure if this fixes your problem as EXC_BAD_ACCESS can mean a number of things, but I see that you get it after receiving a memory warning.
```
2010-08-10 12:35:38.514 cocos2dXrefTest[13501:207] Received memory warning. Level=1
Program received signal: “EXC_BAD_ACCESS”.
```
In my case, the device would crash while trying to load a texture after receiving a memory warning. In the application delegate, this command is called by cocos2d which pretty much does what it's name implies when the device throws a memory warning:
```
- (void)applicationDidReceiveMemoryWarning:(UIApplication *)application {
	[[CCDirector sharedDirector] purgeCachedData];
}
```
So the texture I was trying to load was no longer there and voila... exc_bad_access.

I just commented it out and rewrote the code to manage memory better. Anyways, I'm not sure it applies to what's happening in your case, might be worth a look.
Posted 1 year ago #
Pedagogic368
Member

Thanks so much for the tip. I will try this - I am still running the debugging and have gotten it down to the preMainLoop - [self drawScene];

Look at line # 10 -

#10 0x0001212c in -[CCDisplayLinkDirector preMainLoop:] (self=0x224210, _cmd=0x75fe9, sender=0x243900) /cocos2d/CCDirector.m:1212
#11 0x309d6a08 in CA::Display::DisplayLink::dispatch ()
#12 0x309d6afe in CA::Display::IOMFBDisplayLink::callback ()

What does it mean when the CCDisplayLinkDirector preMainLoop causes EXC_BAD_ACCESS??

Posted 1 year ago #
araker
Moderator

Can you post a complete backtrace? I also suggest upgrading to 0.99.5 beta if you aren't running that version already.

The preMainLoop calls the mainLoop where the updating and drawing is done. So the exc_bad_access can be in almost everything.

If you set a few breakpoints in the mainLoop (in CCDirector.m) and step through the code, you'll probably find the exact line where the exception is generated.

Are you debugging on the simulator or on the device? Sometimes you get a more accurate error description when debugging on the device.

Posted 1 year ago #
Pedagogic368
Member

Hi - I am debugging on the device -

Here is the complete backtrace -

The EXC_BAD_ACCESS is only coming up when I have a UIView that is an EAGLView added to my interface via interface builder. If I change the UIView back to a UIApplication there is no problem - I went back and commented out each line in the .m file of that view and the error still occurred - so then I tried messing with the EAGLView and found out that I could get rid of the problem if I remove it - BUT I need it, any suggestions would be appreciated. I will try the breakpoints in the CCDirector as per your suggestion. Thanks

Program received signal: “EXC_BAD_ACCESS”.
(gdb) bt
#0 0x006ade3e in gleRunVertexSubmitARM ()
#1 0x006ae4a2 in gleLLVMArrayFunc ()
#2 0x006afcc6 in gleSetVertexArrayFunc ()
#3 0x006a87e6 in gleDrawArraysOrElements_ExecCore ()
#4 0x00692a58 in glDrawElements_Exec ()
#5 0x302359a2 in glDrawElements ()
#6 0x0004f3be in -[CCTextureAtlas drawNumberOfQuads:] (self=0x222700, _cmd=0x7f684, n=4) at /cocos2d/CCTextureAtlas.m:306
#7 0x0002163a in -[CCLabelAtlas draw] (self=0x2223e0, _cmd=0x322b8323) /cocos2d/CCLabelAtlas.m:139
#8 0x0001134c in -[CCDirector showFPS] (self=0x21c260, _cmd=0x331b5b3c) /cocos2d/CCDirector.m:904 /cocos2d/CCDirector.m:255
#10 0x00011ff2 in -[CCDisplayLinkDirector preMainLoop:] (self=0x21c260, _cmd=0x75f69, sender=0x202290) at /cocos2d/CCDirector.m:1212
#11 0x309d6a08 in CA::Display::DisplayLink::dispatch ()
#12 0x309d6afe in CA::Display::IOMFBDisplayLink::callback ()
#13 0x337bbdaa in IOMobileFramebufferVsyncNotifyFunc ()
#14 0x33517a82 in ?? ()
#15 0x32c67f40 in __CFMachPortPerform ()
#16 0x32c23d9c in CFRunLoopRunSpecific ()
#17 0x32c234e0 in CFRunLoopRunInMode ()
#18 0x30d620da in GSEventRunModal ()
#19 0x30d62186 in GSEventRun ()
#20 0x314d54c8 in -[UIApplication _run] ()
#21 0x314d39f2 in UIApplicationMain ()
#22 0x000022aa in main (argc=2, argv=0x2ffff5c4) at /main.m:14
(gdb)

Posted 1 year ago #
araker
Moderator

This backtrace says a lot, it seems like you don't have a valid EAGLView. You don't have to step through the code now. I don't have any experience with interface builder, maybe someone else can help you with that. To see if openGL has an issue, could you place "CHECK_GL_ERROR();" somewhere in the mainloop? If there is an error it will show in the console window. This problem is getting interesting..

So which version of cocos are you using exactly? This error reminds me a bit of this issue. Although with that issue there is no IB involved.

Posted 1 year ago #
Pedagogic368
Member

Hello - thanks to everyone for these answers.

The BIG QUESTION is can and EAGLView be a child of a UIView?

I ran a check on using CHECK_GL_ERROR() and nothing shows up in the console. I ran through all the examples from the test files again and the one thing that they all have in common is that the EAGLView is a child of a UIWindow. Every time that I try to run the app set up with a EAGLVIew as a child of a UIView I get the EXEC_BAD_ACCESS error.

You might be asking yourself why I am so determined to set up a view using the EAGLView? Why not just not set up everything as a scene and go from scene to scene. The bottom line for my app is that I need the smooth and elegant page curl transitions of the iphone sdk, (coco2ds has some issues with their page curl transitions) but the animations and effects of/from cocos2d. At this point (and after one solid week of trying I do not think that this is possible - Has anyone EVER created an xib file USING a VIEW and a EAGLVIEW -

all comments and suggestions appreciated.

Posted 1 year ago #
araker
Moderator
Surely this is possible, a EAGLView is a subclassed UIView.

What I forgot to mention, if I change the first line of your code to
```
UIView *newView = [[UIView alloc] initWithFrame:CGRectMake(0,0,320,480)];
//[[UIScreen mainScreen] bounds] would work as well for the frame I guess
```
it works, although nothing appears in screen. But that's probably because the UIView isn't added to the window.
```
[window addSubview: newView];
[window makeKeyAndVisible];
```
So maybe [[UIView mainScreen] bounds] doesn't have the size you would expect it to be.
Posted 1 year ago #
Pedagogic368
Member

Thanks for the suggestion - I will give it a try and let you know!!

Posted 1 year ago #

RSS feed for this topic

Reply

You must log in to post.