How to read and understand the report from Crashlytics - crashlytics

I have a Swift Application, when app is run, sometimes app is crashed. I have received log report about Crash App from Crashlytics but I don't understand log report.
Please help me: How to read and understand report from Crashlytics in order to find line code is error.
My report from Crashlytics:
**Crashed: com.apple.main-thread**
**EXC_BAD_ACCESS KERN_INVALID_ADDRESS 0x0000000000000001**
Thread : Crashed: com.apple.main-thread
0 libGPUSupportMercury.dylib 6691807120 gpus_ReturnNotPermittedKillClient + 12
1 libGPUSupportMercury.dylib 6691811136 gpusSubmitDataBuffers + 172
2 GLEngine 6603264500 gliPresentViewES_Exec + 196
3 GLEngine 6603264248 gliPresentViewES + 84
4 OpenGLES 6603324504 -[EAGLContext presentRenderbuffer:] + 72
5 SpriteKit 6615201312 -[SKView renderContent] + 228
6 SpriteKit 6615188728 __29-[SKView setUpRenderCallback]_block_invoke + 64
7 SpriteKit 6615369448 -[SKDisplayLink _callbackForNextFrame:] + 272
8 QuartzCore 6610051640 CA::Display::DisplayLinkItem::dispatch() + 32
9 QuartzCore 6610051280 CA::Display::DisplayLink::dispatch_items(unsigned long long, unsigned long long, unsigned long long) + 324
10 IOKit 6557291632 IODispatchCalloutFromCFMessage + 376
11 CoreFoundation 6538358212 __CFMachPortPerform + 180
12 CoreFoundation 6538443348 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 56
13 CoreFoundation 6538443188 __CFRunLoopDoSource1 + 436
14 CoreFoundation 6538434868 __CFRunLoopRun + 1640
15 CoreFoundation 6537564884 CFRunLoopRunSpecific + 396
16 GraphicsServices 6699431676 GSEventRunModal + 168
17 UIKit 6617247552 UIApplicationMain + 1488
18 NiftyCat 4296456952 main (AppDelegate.swift:11)
19 libdyld.dylib 6844000776 start + 4
Thanks.

You'll need to Symbolicate your Build to understand your Crash.
To do this in Crashlytics: you must add a "New Run Script Phase". this is the "+" Sign on the Build Phases of your target.
The Script goes like this:
"${PODS_ROOT}/Fabric/run" {YOUR-APP_ID_AT-FABRIC}
If you Installed Fabric using PODS.
Hope this helps ;-)
Cheers

Related

App crashes immediately on start up.. Crash in iOS9 on release only through TestFlight or Store. Distributed with Xcode 8

I have an iPhone app which is crashing on iOS9 devices only after being released through TestFlight or the App Store. The build specs are:
Deployment target 8.1
Base SDK: Latest iOS (iOS 10.1)
Before I post the crash logs I wanted to mention that this app has been on the app store for the past 2 years and has never had issues. We have done 3 updates to the app store this year with 2 of those being after iOS10 was released and there were no issues with iOS9 devices.
The odd thing is that we are using Crashlytics and it has reported over 600 crashes, each one of those a singular crash that points to either an internal apple framework or private API. I have got an iOS 9.2.1 device that is also crashing that I have pulled the logs from. They are starting to follow a trend however I need some help deciphering the cause of the crashes.
Crash 1:
Thread 0 Crashed:
0 libobjc.A.dylib 0x22fb3af6 objc_msgSend + 22
1 libobjc.A.dylib 0x22fc0f8a objc_object::sidetable_release(bool) + 150
2 libobjc.A.dylib 0x22fc13cc (anonymous namespace)::AutoreleasePoolPage::pop(void*) + 388
3 FrontBoardServices 0x24aebc7e -[FBSSerialQueue _performNext] + 242
4 FrontBoardServices 0x24aebf60 -[FBSSerialQueue _performNextFromRunLoopSource] + 44
5 CoreFoundation 0x2379d256 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 14
6 CoreFoundation 0x2379ce46 __CFRunLoopDoSources0 + 454
7 CoreFoundation 0x2379b1ae __CFRunLoopRun + 806
8 CoreFoundation 0x236edbb8 CFRunLoopRunSpecific + 516
9 CoreFoundation 0x236ed9ac CFRunLoopRunInMode + 108
10 UIKit 0x279dfa16 -[UIApplication _run] + 526
11 UIKit 0x279d9fb4 UIApplicationMain + 144
12 Where Next 0x000a7816 main (main.m:16)
13 libdyld.dylib 0x233a0872 start + 2
Crash 2:
Thread 0 Crashed:
0 libobjc.A.dylib 0x22fb3af6 objc_msgSend + 22
1 CoreUI 0x277e3022 -[CUICatalog _resolvedRenditionKeyFromThemeRef:withBaseKey:scaleFactor:devic eIdiom:deviceSubtype:sizeClassHorizontal:sizeClassVertical:memoryClass:graphicsClass:graphicsFallBackOrder:] + 646
2 CoreUI 0x277e2d98 -[CUICatalog _resolvedRenditionKeyForName:scaleFactor:deviceIdiom:deviceSubt ype:sizeClassHorizontal:sizeClassVertical:memoryClass:graphicsClass:graphicsFallBackOrder:withBaseKeySelector:] + 284
3 CoreUI 0x277e252a -[CUICatalog namedLookupWithName:scaleFactor:deviceIdiom:deviceSubtype:sizeClassHorizontal:sizeClassVertical:] + 94
4 UIKit 0x28183a2c __98-[_UIAssetManager imageNamed:scale:idiom:subtype:cachingOptions:sizeClassPair:attachCatalogImage:]_block_invoke + 496
5 UIKit 0x2818377e -[_UIAssetManager imageNamed:scale:idiom:subtype:cachingOptions:sizeClassPair:attachCatalogImage:] + 230
6 UIKit 0x2798bcd4 -[_UIAssetManager imageNamed:scale:idiom:subtype:] + 108
7 UIKit 0x2798bc62 -[_UIAssetManager imageNamed:idiom:subtype:] + 46
8 UIKit 0x2798bc2e -[_UIAssetManager imageNamed:idiom:] + 46
9 UIKit 0x27e1e438 -[UIImageNibPlaceholder initWithCoder:] + 456
10 UIKit 0x27f32180 UINibDecoderDecodeObjectForValue + 780
11 UIKit 0x27f31e68 -[UINibDecoder decodeObjectForKey:] + 296
12 UIKit 0x27e0a602 -[UIButtonContent initWithCoder:] + 382
13 UIKit 0x27f32180 UINibDecoderDecodeObjectForValue + 780
14 UIKit 0x27f3250c UINibDecoderDecodeObjectForValue + 1688
15 UIKit 0x27f31e68 -[UINibDecoder decodeObjectForKey:] + 296
16 UIKit 0x27e0d03c -[UIButton initWithCoder:] + 748
17 UIKit 0x27f32180 UINibDecoderDecodeObjectForValue + 780
18 UIKit 0x27f31e68 -[UINibDecoder decodeObjectForKey:] + 296
19 UIKit 0x27e1d202 -[UIRuntimeConnection initWithCoder:] + 114
20 UIKit 0x27e1d88c -[UIRuntimeEventConnection initWithCoder:] + 52
21 UIKit 0x27f32180 UINibDecoderDecodeObjectForValue + 780
22 UIKit 0x27f32112 UINibDecoderDecodeObjectForValue + 670
23 UIKit 0x27f31e68 -[UINibDecoder decodeObjectForKey:] + 296
24 UIKit 0x27e1c796 -[UINib instantiateWithOwner:options:] + 1110
25 UIKit 0x27cd6676 -[UIViewController _loadViewFromNibNamed:bundle:] + 322
26 UIKit 0x27aab9d6 -[UIViewController loadView] + 142
27 UIKit 0x27971a0a -[UIViewController loadViewIfRequired] + 150
28 UIKit 0x27971958 -[UIViewController view] + 24
29 UIKit 0x281edf4a __67-[UIStoryboardEmbedSegueTemplate newDefaultPerformHandlerForSegue:]_block_invoke + 498
30 UIKit 0x280642d4 -[UIStoryboardSegueTemplate _performWithDestinationViewController:sender:] + 432
31 UIKit 0x28064102 -[UIStoryboardSegueTemplate _perform:] + 66
32 UIKit 0x28064374 -[UIStoryboardSegueTemplate perform:] + 132
33 UIKit 0x27971bca -[UIViewController loadViewIfRequired] + 598
34 UIKit 0x27971958 -[UIViewController view] + 24
35 UIKit 0x279786d0 -[UIWindow addRootViewControllerViewIfPossible] + 68
36 UIKit 0x27975bf2 -[UIWindow _setHidden:forced:] + 278
37 UIKit 0x279ea914 -[UIWindow makeKeyAndVisible] + 48
38 UIKit 0x27c0f11c -[UIApplication _callInitializationDelegatesForMainScene:transitionContext:] + 3320
39 UIKit 0x27c12f0e -[UIApplication _runWithMainScene:transitionContext:completion:] + 1570
40 UIKit 0x27c26c14 __84-[UIApplication _handleApplicationActivationWithScene:transitionContext:completion:]_block_invoke3228 + 36
41 UIKit 0x27c103f6 -[UIApplication workspaceDidEndTransaction:] + 134
42 FrontBoardServices 0x24aebc74 -[FBSSerialQueue _performNext] + 232
43 FrontBoardServices 0x24aebf60 -[FBSSerialQueue _performNextFromRunLoopSource] + 44
44 CoreFoundation 0x2379d256 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 14
45 CoreFoundation 0x2379ce46 __CFRunLoopDoSources0 + 454
46 CoreFoundation 0x2379b1ae __CFRunLoopRun + 806
47 CoreFoundation 0x236edbb8 CFRunLoopRunSpecific + 516
48 CoreFoundation 0x236ed9ac CFRunLoopRunInMode + 108
49 UIKit 0x279dfa16 -[UIApplication _run] + 526
50 UIKit 0x279d9fb4 UIApplicationMain + 144
51 Where Next 0x000e8816 main (main.m:16)
52 libdyld.dylib 0x233a0872 start + 2
Crash 3:
Thread 0 Crashed:
0 libsystem_malloc.dylib 0x2349c43a tiny_free_list_remove_ptr + 126
1 libsystem_malloc.dylib 0x2349b4d0 szone_free_definite_size + 932
2 libcache.dylib 0x2330d6f4 cache_set_name + 20
3 CoreFoundation 0x2372eb94 -[NSCache setName:] + 136
4 CoreUI 0x277e2f0e -[CUICatalog _resolvedRenditionKeyFromThemeRef:withBaseKey:scaleFactor:devic eIdiom:deviceSubtype:sizeClassHorizontal:sizeClassVertical:memoryClass:graphicsClass:graphicsFallBackOrder:] + 370
5 CoreUI 0x277e2d98 -[CUICatalog _resolvedRenditionKeyForName:scaleFactor:deviceIdiom:deviceSubt ype:sizeClassHorizontal:sizeClassVertical:memoryClass:graphicsClass:graphicsFallBackOrder:withBaseKeySelector:] + 284
6 CoreUI 0x277e252a -[CUICatalog namedLookupWithName:scaleFactor:deviceIdiom:deviceSubtype:sizeClassHorizontal:sizeClassVertical:] + 94
7 UIKit 0x28183a2c __98-[_UIAssetManager imageNamed:scale:idiom:subtype:cachingOptions:sizeClassPair:attachCatalogImage:]_block_invoke + 496
8 UIKit 0x2818377e -[_UIAssetManager imageNamed:scale:idiom:subtype:cachingOptions:sizeClassPair:attachCatalogImage:] + 230
9 UIKit 0x28183f50 -[_UIAssetManager imageNamed:withTrait:] + 408
10 UIKit 0x27c4e94c +[UIImage imageNamed:inBundle:compatibleWithTraitCollection:] + 172
11 UIKit 0x27aae536 +[UIImage imageNamed:] + 110
12 Where Next 0x000e555e -[PreferenceObject resetLocations] (PreferenceObject.m:184)
13 Where Next 0x000e4b6e __33+[PreferenceObject sharedManager]_block_invoke (PreferenceObject.m:92)
14 libdispatch.dylib 0x23377dc2 _dispatch_client_callout + 22
15 libdispatch.dylib 0x233789b2 dispatch_once_f + 62
16 Where Next 0x000e4980 +[PreferenceObject sharedManager] (once.h:75)
17 Where Next 0x00102440 -[AppDelegate application:didFinishLaunchingWithOptions:] (AppDelegate.m:57)
18 Where Next 0x002ced6a VMDidFinishLaunchingWithOptions (UIApplication+VMRuntime.m:138)
19 UIKit 0x279e664e -[UIApplication _handleDelegateCallbacksWithOptions:isSuspended:restoreState:] + 394
20 UIKit 0x27c0f032 -[UIApplication _callInitializationDelegatesForMainScene:transitionContext:] + 3086
21 UIKit 0x27c12f0e -[UIApplication _runWithMainScene:transitionContext:completion:] + 1570
22 UIKit 0x27c26c14 __84-[UIApplication _handleApplicationActivationWithScene:transitionContext:completion:]_block_invoke3228 + 36
23 UIKit 0x27c103f6 -[UIApplication workspaceDidEndTransaction:] + 134
24 FrontBoardServices 0x24aebc74 -[FBSSerialQueue _performNext] + 232
25 FrontBoardServices 0x24aebf60 -[FBSSerialQueue _performNextFromRunLoopSource] + 44
26 CoreFoundation 0x2379d256 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 14
27 CoreFoundation 0x2379ce46 __CFRunLoopDoSources0 + 454
28 CoreFoundation 0x2379b1ae __CFRunLoopRun + 806
29 CoreFoundation 0x236edbb8 CFRunLoopRunSpecific + 516
30 CoreFoundation 0x236ed9ac CFRunLoopRunInMode + 108
31 UIKit 0x279dfa16 -[UIApplication _run] + 526
32 UIKit 0x279d9fb4 UIApplicationMain + 144
33 Where Next 0x00103816 main (main.m:16)
34 libdyld.dylib 0x233a0872 start + 2
The last two crashes look like they may be failing on finding an image asset... However because I cannot get this to replicate in debug mode or any form of "run" from Xcode I am stuck.
Appreciate the help community!
The same problem occurs to my app. It crashes in iOS9 on release only through TestFlight or AppStore.
See the accepted answer https://forums.developer.apple.com/thread/60919 . It works for me,and I fixed the bug.
How to resolve "ERROR ITMS-90682: Invalid Bundle - The asset catalog at 'Payload/XXXXX/Assets.car' can't contain 16-bit or P3 assets if the app supports iOS 8 or earlier."
With Xcode 8 GM, this error will occur if you include 16-bit or P3 assets in an app submission targeting iOS releases earlier then iOS 9.3. If your app requires wide color functionality you must change your Deployment Target to iOS 9.3 or later. If your app does not require wide color functionality and you wish to deploy it to older iOS versions then you should replace all 16-bit or P3 assets with 8-bit sRGB assets. You can find 16-bit or P3 assets by running “assetutil” on the asset catalog named in the error message from iTunes Connect. The following steps outline the process:
Create an Inspectable .ipa file. In the Xcode Organizer (Xcode->Window->Organizer), select an archive to inspect, click “Export...", and choose "Export for Enterprise or Ad-Hoc Deployment". This will create a local copy of the .ipa file for your app.
Locate that .ipa file and change its the extension to .zip.
Expand the .zip file. This will produce a Payload folder containing your .app bundle.
Open a terminal and change the working directory to the top level of your .app bundle cd path/to/Payload/your.app
Use the find tool to locate Assets.car files in your .app bundle as shown below: find . -name 'Assets.car'
Use the assetutil tool to find any 16-bit or P3 assets, in each Assets.car your application has as shown below. : sudo xcrun --sdk iphoneos assetutil --info /path/to/a/Assets.car > /tmp/Assets.json
Examine the resulting /tmp/Assets.json and look for any contents containing “DisplayGamut": “P3” and its associated “Name". This will be the name of your imageset containing one or more 16-bit or P3 assets.
Replace those assets with 8-bit / sRGB assets, then rebuild your app.
Update: If your Deployment Target is set to either 8.3 or 8.4 and you have an asset catalog then you will receive this same error message, even if you do not actually have 16-bit or P3 assets. In this case you will either need to lower your Deployment Target to 8.2, or move it up to 9.x.
Release crashes (crashes that happen on builds sent through the App Store or TestFlight) can be tough to nail down. I had one which was crashing on NSArray's containsObject: function, and could not reproduce it myself, or so I thought.
I did the following to reproduce the bug.
Went to Product -> Scheme -> Edit Scheme...
Clicked on the "Info" tab for my standard debug scheme
Changed the build configuration from "Debug" to "Release"
Rebuilt and ran the project
In some cases, this is not enough to reproduce a release crash. I did the next steps to reproduce it.
Unchecked the "Debug Executable" within that earlier Info tab on the scheme
Cleaned my project and build folder (Command-Shift-K and Command-Alt-Shift-K respectively)
Rebuilt and ran the project
Here is what it would look like on my configuration if I needed to do the same thing.
Once you are able to reproduce the crash (hopefully you can reproduce with logs), try your usual debugging methods to see where it is crashing. Play a sound when something executes, comment out lines, etc.
I unfortunately can't know your exact crash, though this method above helped me reproduce an issue 90% of our users were having and I wasn't, simply because I was building on debug before.

Random iOS 6 crash with iOS 7 SDK

My current main Application is randomly crashing on iOS 6 devices when i compile with iOS 7. It is system deep i think and don't know how to fix this little nasty bug. In my App there are plenty of iOS 6 user with this crash and it's driving me nuts.
Thread : Fatal Exception: NSGenericException
0 CoreFoundation 0x32b902a3 __exceptionPreprocess + 162
1 libobjc.A.dylib 0x3a8b897f objc_exception_throw + 30
2 CoreFoundation 0x32b8fd85 -[NSException name]
3 UIKit 0x34d22f75 __54+[_UIAppearance _recordersExcludingSource:withWindow:]_block_invoke_0 + 332
4 CoreFoundation 0x32b8d62f __NSDictionaryEnumerate + 714
5 UIKit 0x34d22e1d +[_UIAppearance _recordersExcludingSource:withWindow:] + 136
6 UIKit 0x34e013a5 UIViewServiceCurrentAppearanceSerializedRepresentations + 60
7 UIKit 0x34d8f7c7 -[_UIRemoteViewControllerConnectionRequest _sendServiceViewControllerRequest] + 206
8 UIKit 0x34d8f65d __block_global_5 + 264
9 libdispatch.dylib 0x3acd39f7 _dispatch_barrier_sync_f_invoke + 30
10 UIKit 0x34d8f551 __76-[_UIRemoteViewControllerConnectionRequest _connectToViewControllerOperator]_block_invoke_0 + 92
11 UIKit 0x34d98bc5 __block_global_0 + 32
12 libdispatch.dylib 0x3acd53f7 dispatch_once_f$VARIANT$mp + 42
13 UIKit 0x34d98ba1 __73-[_UIViewServiceSessionEndpoint connectToDeputyOfType:connectionHandler:]_block_invoke_0 + 88
14 libdispatch.dylib 0x3acd011f _dispatch_call_block_and_release + 10
15 libdispatch.dylib 0x3acd3ecf _dispatch_queue_drain$VARIANT$mp + 142
16 libdispatch.dylib 0x3acd3dc1 _dispatch_queue_invoke$VARIANT$mp + 40
17 libdispatch.dylib 0x3acd491d _dispatch_root_queue_drain + 184
18 libdispatch.dylib 0x3acd4ac1 _dispatch_worker_thread2 + 84
19 libsystem_c.dylib 0x3ad04a11 _pthread_wqthread + 360
20 libsystem_c.dylib 0x3ad048a4 start_wqthread + 8
Add a Exception breakpoint you will get some more info about your crash.. for adding a Exception Breakpoint have a look on this https://developer.apple.com/library/ios/recipes/xcode_help-breakpoint_navigator/articles/adding_an_exception_breakpoint.html
Add breakpoints step into every line of code to find the bug , Or maybe this would help you read crash reports. http://www.raywenderlich.com/23704/demystifying-ios-application-crash-logs

iOS5 - KERN_INVALID_ADDRESS in crash log

I need your help to understand what's going on in this crash log for my app on iPhone 4S.
Date/Time: 2011-10-23 07:51:33.669 -0700
OS Version: iPhone OS 5.0 (9A334)
Report Version: 104
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0xc0000008
Crashed Thread: 0
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libobjc.A.dylib 0x3205afbc objc_msgSend + 16
1 UIKit 0x31a19b68 -[UIAnimator stopAnimation:] + 412
2 UIKit 0x31a195d4 -[UIAnimator(Static) _advance:withTimestamp:] + 260
3 UIKit 0x31a194c6 -[UIAnimator(Static) _LCDHeartbeatCallback:] + 46
4 QuartzCore 0x3166441c CA::Display::DisplayLink::dispatch(unsigned long long, unsigned long long)+ 160
5 QuartzCore 0x31664372 CA::Display::IOMFBDisplayLink::callback(__IOMobileFramebuffer*, unsigned long long, unsigned long long, unsigned long long, void*) + 54
6 IOMobileFramebuffer 0x32c58f8c IOMobileFramebufferVsyncNotifyFunc + 76
7 IOKit 0x34ea188a IODispatchCalloutFromCFMessage + 182
8 CoreFoundation 0x36cb9f3c __CFMachPortPerform + 356
9 CoreFoundation 0x36cc454c __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 32
10 CoreFoundation 0x36cc44ee __CFRunLoopDoSource1 + 134
11 CoreFoundation 0x36cc333c __CFRunLoopRun + 1364
12 CoreFoundation 0x36c464d6 CFRunLoopRunSpecific + 294
13 CoreFoundation 0x36c4639e CFRunLoopRunInMode + 98
14 GraphicsServices 0x32921fe6 GSEventRunModal + 150
15 UIKit 0x318f673c UIApplicationMain + 1084
16 MyAppPro 0x0000214a main (main.m:13)
17 MyAppPro 0x00002108 start + 32
This link to a discussion in Developer Forums seems to imply bad hardware!?
A little confused!
Thanks.
Your question is a dupe of many other questions that involve EXC_BAD_ACCESS crashes.
Like this one:
how to understand Crash Log of iPhone
Why not step through your program and see if you can isolate where the crash is triggered?
The article you linked is talking about a Macintosh error with Safari, totally different than what you are experiencing.

Debugging an iPad device crash with little info

I'm getting the following stack trace from an iPad crash pulled from the device. This was pulled from a user's iPad and I don't know what they were doing when it crashed. How would I get more info on why/where the app is crashing and fix it?
Uncaught C++ Exception
Stack trace:
0 - 0 MyApp 0x00005ac1 _Z16TerminateHandlerv + 24
1 - 1 libstdc++.6.dylib 0x33814e3d _ZN10__cxxabiv111__terminateEPFvvE + 52
2 - 2 libstdc++.6.dylib 0x33814e91 _ZSt9terminatev + 16
3 - 3 libstdc++.6.dylib 0x33814f61 __cxa_throw + 84
4 - 4 libobjc.A.dylib 0x3441dc8b objc_exception_throw + 70
5 - 5 Foundation 0x3645192b __NSThreadPerformPerform + 654
6 - 6 CoreFoundation 0x34e16a79 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 12
7 - 7 CoreFoundation 0x34e1875f __CFRunLoopDoSources0 + 382
8 - 8 CoreFoundation 0x34e194eb __CFRunLoopRun + 230
9 - 9 CoreFoundation 0x34da9ec3 CFRunLoopRunSpecific + 230
10 - 10 CoreFoundation 0x34da9dcb CFRunLoopRunInMode + 58
11 - 11 GraphicsServices 0x339d041f GSEventRunModal + 114
12 - 12 GraphicsServices 0x339d04cb GSEventRun + 62
13 - 13 UIKit 0x33a07d69 -[UIApplication _run] + 404
14 - 14 UIKit 0x33a05807 UIApplicationMain + 670
15 - 15 MyApp 0x000036af main + 70
16 - 16 MyApp 0x00003664 start + 40
Two things you might try:
Somtimes apps crash and the debugger stops on a completely different method. Enable "guard malloc" in the xcode run settings (under schemes in xcode4), run the app in the debugger utill it crashes, and see if that shows you which method is to blame.
If not, your best bet is to run the app in the debugger and make the crash happen. Try everything, simulate memory warnings everywhere, use every feature of the app, try every possible combination of paths through the app. Asking the user what they think they were doing might narrow it down some.

xcode instruments causing app crash

I am using xcode Instruments to track Allocations and Leaks. My app is crashing though. It does not crash when running the regular debug or release builds standalone, only when under Instruments:
Any thoughts ideas very gratefully received....
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0002b2e0
Crashed Thread: 0
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0 Crashed:
0 libobjc.A.dylib 0x34499c96 objc_msgSend + 14
1 ZZZ Test Suite 0x000a3d74 0x95000 + 60788
2 CoreFoundation 0x308e4c3c -[NSObject(NSObject) release] + 24
3 CoreFoundation 0x308e519a CFRelease + 62
4 CoreFoundation 0x308e7eb4 _CFAutoreleasePoolPop + 140
5 Foundation 0x341b41c4 -[NSAutoreleasePool release] + 92
6 UIKit 0x309e5f08 _UIApplicationHandleEvent + 5784
7 GraphicsServices 0x30269e70 PurpleEventCallback + 660
8 CoreFoundation 0x30957a90 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 20
9 CoreFoundation 0x30959838 __CFRunLoopDoSource1 + 160
10 CoreFoundation 0x3095a606 __CFRunLoopRun + 514
11 CoreFoundation 0x308eaebc CFRunLoopRunSpecific + 224
12 CoreFoundation 0x308eadc4 CFRunLoopRunInMode + 52
13 GraphicsServices 0x30269418 GSEventRunModal + 108
14 GraphicsServices 0x302694c4 GSEventRun + 56
15 UIKit 0x30a10d62 -[UIApplication _run] + 398
16 UIKit 0x30a0e800 UIApplicationMain + 664
17 ZZZ Test Suite 0x0009665c 0x95000 + 5724
18 ZZZ Test Suite 0x00096604 0x95000 + 5636
Try running it through the analyser first. You can run it from xcode from the |product| menu then select Analyze. It's a static analyser (clang) that analyses your code when it builds so any problems causing your code to crash at runtime could well be visible through static analysis. Give it a try and fix any problems it throws up then try instruments again.
As a complement to what Ian says above:
set the Environment variable "NSZombieEnabled" to YES
and you will hopefully have a more informative fail.
(In XCode 4 the Environment Variables is found under "Edit Scheme" and select "Debug")