Hi Shoes, What does the code for your custom UITableViewCell look like?
My *guess* is that the cell isn't holding a reference to some objects that it is passing along to objective-c and that the GC is collecting said object(s), thus when objective-c tries to invoke something on those objects, the above crash occurs. Jeff On Tue, Nov 1, 2011 at 12:45 PM, Shoes <[email protected]> wrote: > I have an app that works fine in IOS 4. When users upgrade to iOS 5, that > app > crashes. > > The app crashes in a Table View, I have a custom cell view. When the user > clicks a on a cell, the app crashes. Any help would be appreciated. If > anyone knows if Xamarin is coming out with an update that repairs this as > well, please let me know. Here is the error message I receive on crash: > > Stacktrace: > > at (wrapper managed-to-native) > MonoTouch.UIKit.UIApplication.UIApplicationMain > (int,string[],intptr,intptr) > <IL 0x0009f, 0xffffffff> > at MonoTouch.UIKit.UIApplication.Main (string[],string,string) [0x00042] > in /Developer/MonoTouch/Source/monotouch/src/UIKit/UIApplication.cs:29 > at MonoTouch.UIKit.UIApplication.Main (string[]) [0x00000] in > /Developer/MonoTouch/Source/monotouch/src/UIKit/UIApplication.cs:34 > at RxNTClient4.Application.Main (string[]) [0x00000] in > /Users/rxnt/Documents/Projects/RxNTClient4/RxNTClient4/Main.cs:28 > at (wrapper runtime-invoke) <Module>.runtime_invoke_void_object > (object,intptr,intptr,intptr) <IL 0x00050, 0xffffffff> > > Native stacktrace: > > 0 RxNTClient4 0x000e1108 > mono_handle_native_sigsegv + 408 > 1 RxNTClient4 0x00011e8f > mono_sigsegv_signal_handler + 351 > 2 libSystem.B.dylib 0x954b205b _sigtramp + 43 > 3 ??? 0xffffffff 0x0 + 4294967295 > 4 UIKit 0x01d061b5 -[UIControl > sendAction:to:forEvent:] + 67 > 5 UIKit 0x01d08647 > -[UIControl(Internal) > _sendActionsForEvents:withEvent:] + 527 > 6 UIKit 0x01d071f4 -[UIControl > touchesEnded:withEvent:] + 458 > 7 UIKit 0x01f02987 > _UIGestureRecognizerSortAndSendDelayedTouches + 3609 > 8 UIKit 0x01f030fc > _UIGestureRecognizerUpdateObserver + 927 > 9 CoreFoundation 0x00e8efbb > __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 27 > 10 CoreFoundation 0x00e240e7 > __CFRunLoopDoObservers + > 295 > 11 CoreFoundation 0x00decbd7 __CFRunLoopRun + > 1575 > 12 CoreFoundation 0x00dec240 > CFRunLoopRunSpecific + > 208 > 13 CoreFoundation 0x00dec161 > CFRunLoopRunInMode + 97 > 14 GraphicsServices 0x03f4c268 GSEventRunModal > + 217 > 15 GraphicsServices 0x03f4c32d GSEventRun + 115 > 16 UIKit 0x01c8642e > UIApplicationMain + 1160 > 17 ??? 0x07feea34 0x0 + 134146612 > 18 ??? 0x07fee900 0x0 + 134146304 > 19 ??? 0x07fee1f8 0x0 + 134144504 > 20 ??? 0x07fee144 0x0 + 134144324 > 21 ??? 0x07fee1cf 0x0 + 134144463 > 22 RxNTClient4 0x00011bdf > mono_jit_runtime_invoke > + 1407 > 23 RxNTClient4 0x0022020a > mono_runtime_invoke + > 170 > 24 RxNTClient4 0x00222f41 > mono_runtime_exec_main + > 705 > 25 RxNTClient4 0x00222151 > mono_runtime_run_main + > 929 > 26 RxNTClient4 0x000ad7cf mono_jit_exec + > 239 > 27 RxNTClient4 0x002f420a main + 5194 > 28 RxNTClient4 0x00003435 start + 53 > > ================================================================= > Got a SIGSEGV while executing native code. This usually indicates > a fatal error in the mono runtime or one of the native libraries > used by your application. > ================================================================= > > -- > View this message in context: > http://monotouch.2284126.n4.nabble.com/Crash-in-iOS-5-tp3964288p3964288.html > Sent from the MonoTouch mailing list archive at Nabble.com. > _______________________________________________ > MonoTouch mailing list > [email protected] > http://lists.ximian.com/mailman/listinfo/monotouch >
_______________________________________________ MonoTouch mailing list [email protected] http://lists.ximian.com/mailman/listinfo/monotouch
