[MonoTouch] Can somebody interpret this crash?
Rolf Bjarne Kvinge
rolf at xamarin.com
Fri Oct 28 03:45:56 EDT 2011
Hi,
This is a crash in native code, which mono can't handle and the
process will be killed.
In this case what is likely happening is that you have managed objects
only objective c has a reference too - this means the GC thinks it can
free them. When some time later objective c tries to use those objects
it will crash like this.
3 ??? 0xffffffff 0x0 + 4294967295
4 UIKit 0x01e933b0
-[UITableViewRowData invalidateAllSections] + 66
This is the objective c method trying to call managed code, I would
try to figure out which managed code it's trying to call and ensure
that the corresponding object isn't freed by the GC too early (for
instance ensuring it's accessible from a class-level variable instead
of a method-level variable) - the exact solution will of course depend
on the exact problem.
I hope this helps.
Rolf
On Thu, Oct 27, 2011 at 8:14 PM, René Ruppert
<rene.ruppert at googlemail.com> wrote:
> And the fact that I do not get a Monotouch exception? How is that possible? Could it be that it is a view that is still floating around in ObjC without connection to the managed world?
> Also if I debug it does not break anywhere with a NULL exception, it just dies. How could I localize the issue? Any hints?
> My best guess are currently the "zombie" views. I have something in mind where that could happen and I think MGSplitViewController might be suffering from the same issue if somebody uses it the same way.
>
> René
>
> -----Ursprüngliche Nachricht-----
> Von: Nic Wise [mailto:nicw at fastchicken.co.nz]
> Gesendet: Donnerstag, 27. Oktober 2011 17:59
> An: Krumelur
> Cc: monotouch at lists.ximian.com
> Betreff: Re: [MonoTouch] Can somebody interpret this crash?
>
> "mono_handle_native_sigsegv"
>
> Null Reference exception (SegV = Segment Violation)
>
> this:
>
> UITableViewRowData
>> invalidateAllSections
>
> makes it look like it might be in a UITableView related item?
>
>
> On Thu, Oct 27, 2011 at 16:04, Krumelur <rene.ruppert at gmail.com> wrote:
>> I am getting this sometimes when rotating the simulator/device. Can
>> anybody make sense of the output and give me a hint? I've been trying
>> to debug for some hours now:
>>
>> Stacktrace:
>>
>> at (wrapper managed-to-native)
>> MonoTouch.ObjCRuntime.Messaging.void_objc_msgSendSuper_IntPtr
>> (intptr,intptr,intptr) <IL 0x00025, 0xffffffff>
>> at MonoTouch.UIKit.UIApplication.SendEvent (MonoTouch.UIKit.UIEvent)
>> [0x00037] in
>> /Developer/MonoTouch/Source/monotouch/src/UIKit/UIApplication.g.cs:170
>> at TestApp.UIApplicationMain.SendEvent (MonoTouch.UIKit.UIEvent)
>> [0x00000] in
>> /Users/iBrainloop/Documents/Develop/BrainloopMobile106/TestApp/TestApp
>> /UIApplicationMain.cs:23
>> at (wrapper runtime-invoke)
>> <Module>.runtime_invoke_void__this___object
>> (object,intptr,intptr,intptr) <IL 0x00052, 0xffffffff>
>> 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 TestApp.Application.Main (string[]) [0x00000] in
>> /Users/iBrainloop/Documents/Develop/BrainloopMobile106/TestApp/TestApp
>> /Main.cs:15
>> at (wrapper runtime-invoke) <Module>.runtime_invoke_void_object
>> (object,intptr,intptr,intptr) <IL 0x00050, 0xffffffff>
>>
>> Native stacktrace:
>>
>> 0 TestApp 0x000d1e9c
>> mono_handle_native_sigsegv + 343
>> 1 TestApp 0x000100e0
>> mono_sigsegv_signal_handler + 322
>> 2 libsystem_c.dylib 0x91e4259b _sigtramp +
>> 43
>> 3 ??? 0xffffffff 0x0 +
>> 4294967295
>> 4 UIKit 0x01e933b0
>> -[UITableViewRowData invalidateAllSections] + 66
>> 5 UIKit 0x01d4ad23
>> -[UITableView(_UITableViewPrivate) _updateRowData] + 113
>> 6 UIKit 0x01d4ef35
>> -[UITableView _rectChangedWithNewSize:oldSize:] + 164
>> 7 UIKit 0x01d4d917
>> -[UITableView setFrame:]
>> + 266
>> 8 UIKit 0x01d0da03
>> -[UIView(Geometry) resizeWithOldSuperviewSize:] + 385
>> 9 UIKit 0x01d1197b
>> -[UIView(Geometry) resizeSubviewsWithOldSize:] + 273
>> 10 UIKit 0x01d0de94
>> -[UIView(Geometry) setFrame:] + 497
>> 11 UIKit 0x01d0da03
>> -[UIView(Geometry) resizeWithOldSuperviewSize:] + 385
>> 12 UIKit 0x01d1197b
>> -[UIView(Geometry) resizeSubviewsWithOldSize:] + 273
>> 13 UIKit 0x01d0e1c5
>> -[UIView(Geometry) setBounds:] + 623
>> 14 UIKit 0x01d894f7
>> -[UIViewController
>> window:willAnimateRotationToInterfaceOrientation:duration:] + 440
>> 15 UIKit 0x01d0055f -[UIWindow
>> _setRotatableClient:toOrientation:updateStatusBar:duration:force:] +
>> 4347
>> 16 UIKit 0x01cfa254 -[UIWindow
>> _setRotatableViewOrientation:duration:force:] + 89
>> 17 UIKit 0x01cfd2b9 -[UIWindow
>> _updateInterfaceOrientationFromDeviceOrientation:] + 164
>> 18 Foundation 0x013ff669
>> _nsnote_callback + 145
>> 19 CoreFoundation 0x00e9d9f9
>> __CFXNotificationPost_old + 745
>> 20 CoreFoundation 0x00e1c93a
>> _CFXNotificationPostNotification + 186
>> 21 Foundation 0x013f520e
>> -[NSNotificationCenter postNotificationName:object:userInfo:] + 134
>> 22 UIKit 0x01e8e00a -[UIDevice
>> setOrientation:animated:] + 228
>> 23 UIKit 0x01ce6039
>> -[UIApplication handleEvent:withNewEvent:] + 4127
>> 24 UIKit 0x01cddabf
>> -[UIApplication sendEvent:] + 71
>> 25 ??? 0x0dacc804 0x0 +
>> 229427204
>> 26 ??? 0x0dacc760 0x0 +
>> 229427040
>> 27 ??? 0x0dacc388 0x0 +
>> 229426056
>> 28 ??? 0x0dacc606 0x0 +
>> 229426694
>> 29 TestApp 0x0000fe9b
>> mono_jit_runtime_invoke + 1332
>> 30 TestApp 0x001ee961 mono_runtime_invoke +
>> 137
>> 31 TestApp 0x0029f964 monotouch_trampoline
>> + 2527
>> 32 UIKit 0x01ce2f2e
>> _UIApplicationHandleEvent + 7576
>> 33 GraphicsServices 0x040a7992
>> PurpleEventCallback +
>> 1550
>> 34 CoreFoundation 0x00ea6944
>> __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE1_PERFORM_FUNCTION__ + 52
>> 35 CoreFoundation 0x00e06cf7
>> __CFRunLoopDoSource1 +
>> 215
>> 36 CoreFoundation 0x00e03f83
>> __CFRunLoopRun + 979
>> 37 CoreFoundation 0x00e03840
>> CFRunLoopRunSpecific +
>> 208
>> 38 CoreFoundation 0x00e03761
>> CFRunLoopRunInMode + 97
>> 39 GraphicsServices 0x040a61c4
>> GSEventRunModal + 217
>> 40 GraphicsServices 0x040a6289 GSEventRun +
>> 115
>> 41 UIKit 0x01ce6c93
>> UIApplicationMain + 1160
>> 42 ??? 0x0a2407e5 0x0 +
>> 170133477
>> 43 ??? 0x0a23f018 0x0 +
>> 170127384
>> 44 ??? 0x0a23ed10 0x0 +
>> 170126608
>> 45 ??? 0x0a23ee66 0x0 +
>> 170126950
>> 46 TestApp 0x0000fe9b
>> mono_jit_runtime_invoke + 1332
>> 47 TestApp 0x001ee961 mono_runtime_invoke +
>> 137
>> 48 TestApp 0x001f1048
>> mono_runtime_exec_main + 669
>> 49 TestApp 0x001f0432 mono_runtime_run_main
>> + 843
>> 50 TestApp 0x000a3f9e mono_jit_exec + 200
>> 51 TestApp 0x002a3d21 main + 3733
>> 52 TestApp 0x00003179 _start + 208
>> 53 TestApp 0x000030a8 start + 40
>> 54 ??? 0x00000002 0x0 + 2
>>
>> =================================================================
>> 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/Can-somebody-interpret-this-cra
>> sh-tp3944809p3944809.html Sent from the MonoTouch mailing list archive
>> at Nabble.com.
>> _______________________________________________
>> MonoTouch mailing list
>> MonoTouch at lists.ximian.com
>> http://lists.ximian.com/mailman/listinfo/monotouch
>>
>
>
>
> --
> Nic Wise
> t. +44 7788 592 806 | @fastchicken | http://www.linkedin.com/in/nicwise
> b. http://www.fastchicken.co.nz/
>
> Nearest Bus: find when the next bus is coming to your stop. http://goo.gl/Vcz1p mobileAgent (for FreeAgent): get your accounts in your pocket.
> http://goo.gl/IuBU
> Trip Wallet: Keep track of your budget on the go: http://goo.gl/ePhKa London Bike App: Find the nearest Boris Bike, and get riding! http://goo.gl/Icp2
>
> _______________________________________________
> MonoTouch mailing list
> MonoTouch at lists.ximian.com
> http://lists.ximian.com/mailman/listinfo/monotouch
>
More information about the MonoTouch
mailing list