Some random crash EXC_BAD_ACCESS?

Check your (void)dealloc method. I was getting the same thing and in my dealloc method I was calling super dealloc first before releasing every else. Right way.

Check your -(void)dealloc method. I was getting the same thing and in my dealloc method I was calling super dealloc first before releasing every else. Right way -(void)dealloc { // Right way myObj release; super dealloc; } I had it this way and it crashed everytime I dismissed my view.

-(void)dealloc { // Wrong way super dealloc; myObj release; }.

Dododedodonl said in a comment that the app is compiled with ARC, so super dealloc is not allowed. Good suggestion for non-ARC builds, though. – Rob Bajorek Nov 4 at 1:07 Thanks for the info.

I haven't gotten into ARC yet. Still trying to figure out some of the basics. – syclonefx Nov 4 at 1:11 Thanks syclonefx, but as RobBajorek said, I compile with ARC.

This is the reason why I think it is strange, that my AppDelegate gets released somehow... – dododedodonl Nov 4 at 10:36.

Idea 1 Check that your tabBar is linked/retained. It seems to be deallocated at some time. When the modal view is dismissed, put some beakpoints to check that the reference is still valid.

Idea 2 Don't you have any property(copy) or variable that you are trying to copy without having implemented and declared the NSCopying protocol in the object itself? If yes, don't you have some problems into the implementation itself? Idea 3 Deactivate ARC and test if the problem is still there (if you don't use huge memory in your app of course because of memory leaks that will generate).

– Oliver Nov 7 at 22:43 haven't tried this one yet, because I have to write memory management code for all my code... And I'm not that good in memory management... – dododedodonl Nov 7 at 22:49.

As per the crash, 12: 0x76d6b7 in -UINibDecoder decodeObjectForKey: 13: 0x66e305 in -UINib instantiateWithOwner:options: It shows, the nib file is not binded correctly with the view of some particular tab. Please check, if in AppDelegate, you are making call to the view controller with correct nib name, before adding to the tab bar.

As a hunch you are crashing because you don't have enough memory left. One of the relevant views or view controllers is being held because its referenced under ARC as strong when weak would be more appropriate. Also go looking in your code for instances of respondsToSelector: .

It might not be the delegate that is trying to be messaged in this instance. It's a red herring. My experience is that those "sent to deallocated instance" console logs rarely tell you the actual object which was being messaged.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.