Bug 8230 - Push/Pop Crash
Summary: Push/Pop Crash
Status: RESOLVED NOT_REPRODUCIBLE
Alias: None
Product: iOS
Classification: Xamarin
Component: General ()
Version: 6.0.x
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2012-11-05 15:39 UTC by Pierce Boggan [MSFT]
Modified: 2014-04-10 12:03 UTC (History)
2 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.


Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:
Status:
RESOLVED NOT_REPRODUCIBLE

Description Pierce Boggan [MSFT] 2012-11-05 15:39:44 UTC
I have a basic app that has a navigation controller. I have a maximum of two view controllers pushed on the navigation controller. Just to give you an idea on memory usage; the pushed view controllers have a table view and a search display controller.

The application is crashing when I repeatedly push and pop these two view controllers. I could not figure out how to reproduce it in a consistent manner. Sometimes, it crashes after two cycles of push/pop and sometimes it takes longer. By cycle I mean that when at the root view controller, push the first VC, then push the second, then pop the second, then pop the first. After a couple of cycles, it crashes when pushing the first VC.

Here is the stack trace from the 'Application Output' window:

======


Stacktrace:

at (wrapper managed-to-native) MonoTouch.ObjCRuntime.Messaging.void_objc_msgSend (intptr,intptr) <IL 0x00024, 0xffffffff>
at MonoTouch.Foundation.NSObject.FinishDispose () [0x0000b] in /Developer/MonoTouch/Source/monotouch/src/Foundation/NSObject.cs:158
at MonoTouch.Foundation.NSObject/MonoTouch_Disposer.Drain (MonoTouch.Foundation.NSObject) [0x00062] in /Developer/MonoTouch/Source/monotouch/src/Foundation/NSObject.cs:376
at (wrapper runtime-invoke) <Module>.runtime_invoke_void_object (object,intptr,intptr,intptr) <IL 0x00050, 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) [0x0004c] in /Developer/MonoTouch/Source/monotouch/src/UIKit/UIApplication.cs:38
at OmApp.Application.Main (string[]) [0x00000] in /Users/yahya/Projects/OmApp/OmApp/Main.cs:17
at (wrapper runtime-invoke) <Module>.runtime_invoke_void_object (object,intptr,intptr,intptr) <IL 0x00050, 0xffffffff>

Native stacktrace:

0 OmApp 0x0009152c mono_handle_native_sigsegv + 284
1 OmApp 0x000062b8 mono_sigsegv_signal_handler + 248
2 libsystem_c.dylib 0x916bc59b _sigtramp + 43
3 ??? 0xffffffff 0x0 + 4294967295
4 UIKit 0x0253d541 -[UISearchDisplayController dealloc] + 105
5 libobjc.A.dylib 0x03701e3d _objc_rootRelease + 47
6 ??? 0x0e3ffa14 0x0 + 239073812
7 ??? 0x11a89050 0x0 + 296259664
8 ??? 0x11a88efc 0x0 + 296259324
9 ??? 0x09a91976 0x0 + 162077046
10 OmApp 0x0000a672 mono_jit_runtime_invoke + 722
11 OmApp 0x0016c0ae mono_runtime_invoke + 126
12 OmApp 0x00210e55 monotouch_static_trampoline + 3445
13 CoreFoundation 0x011ddd51 +[NSObject performSelector:withObject:] + 65
14 Foundation 0x017579df __NSThreadPerformPerform + 254
15 CoreFoundation 0x011b094f __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 15
16 CoreFoundation 0x01113b43 __CFRunLoopDoSources0 + 243
17 CoreFoundation 0x01113424 __CFRunLoopRun + 1012
18 CoreFoundation 0x01112d84 CFRunLoopRunSpecific + 212
19 CoreFoundation 0x01112c9b CFRunLoopRunInMode + 123
20 GraphicsServices 0x048307d8 GSEventRunModal + 190
21 GraphicsServices 0x0483088a GSEventRun + 103
22 UIKit 0x0225f626 UIApplicationMain + 1163
23 ??? 0x0e3fabb5 0x0 + 239053749
24 ??? 0x0e3f87f8 0x0 + 239044600
25 ??? 0x0e3f7b90 0x0 + 239041424
26 ??? 0x0e3f7ce6 0x0 + 239041766
27 OmApp 0x0000a672 mono_jit_runtime_invoke + 722
28 OmApp 0x0016c0ae mono_runtime_invoke + 126
29 OmApp 0x00170234 mono_runtime_exec_main + 420
30 OmApp 0x00175625 mono_runtime_run_main + 725
31 OmApp 0x000678c5 mono_jit_exec + 149
32 OmApp 0x00203e51 main + 2209
33 OmApp 0x00003675 start + 53
34 ??? 0x00000004 0x0 + 4

=================================================================
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.
=================================================================
Comment 2 Pierce Boggan [MSFT] 2012-11-30 19:53:04 UTC
Are there any known workarounds for things like this?
Comment 3 Rolf Bjarne Kvinge [MSFT] 2012-11-30 20:01:41 UTC
Not calling ReleaseDesignerOutlets seems to fix it.
Comment 4 Rolf Bjarne Kvinge [MSFT] 2014-04-10 12:03:52 UTC
I can't reproduce this anymore with Xamarin.iOS 7.2.1

Please reopen if it's still happening to you.