Bug 5388 - Uncatchable crash in wapi_disconnectex
Summary: Uncatchable crash in wapi_disconnectex
Alias: None
Product: iOS
Classification: Xamarin
Component: XI runtime ()
Version: 5.2
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Bugzilla
Depends on:
Reported: 2012-05-29 05:11 UTC by Matt Jones
Modified: 2013-12-05 18:35 UTC (History)
2 users (show)

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:

Description Matt Jones 2012-05-29 05:11:27 UTC
I keep getting a crash inside wapi_disconnectex as I shut down. It's difficult to recreate. I've listed the stack trace below just to see if it jogs anybody's memory.

[ Before the Socket.Disconnect I call Socket.Shutdown(SocketShutdown.Both) ]

0 TradeClient1 0x00047916 testflight_backtrace + 142
1 TradeClient1 0x000484a4 TFSignalHandler + 212
2 libsystem_c.dylib 0x339d67ec _sigtramp + 48
3 TradeClient1 0x0091e9e8 wapi_disconnectex (sockets.c:1103)
4 TradeClient1 0x009071ea ves_icall_System_Net_Sockets_Socket_Disconnect_internal (socket-io.c:1429)
5 TradeClient1 0x00125aeb wrapper_managed_to_native_System_Net_Sockets_Socket_Disconnect_internal_intptr_bool_int_ (System.dll.7.s:205496)
6 TradeClient1 0x00848d8b Comms_SaturnTrader_ClientCore_Comms_LowLevel_AsynchronousSocket_CleanUp (Comms.dll.7.s:9976)
7 TradeClient1 0x00848993 Comms_SaturnTrader_ClientCore_Comms_LowLevel_AsynchronousSocket_Disconnect (Comms.dll.7.s:9515)
8 TradeClient1 0x0084f11f Comms_SaturnTrader_ClientCore_Comms_VirtualConnectionTCP_Disconnect (Comms.dll.7.s:19447)
9 TradeClient1 0x0084c067 Comms_SaturnTrader_ClientCore_Comms_VirtualConnectionBaseClient_Disconnect (Comms.dll.7.s:14764)
10 TradeClient1 0x0022259f Connector_SaturnTrader_ClientCore_Connector_SpreadCoConnector_Logoff (Connector.dll.7.s:6738)
11 TradeClient1 0x0062c64f TradeClient1_TradeClient1_AppDelegate_DidEnterBackground_MonoTouch_UIKit_UIApplication (TradeClient1.exe.7.s:2603)
12 TradeClient1 0x0049b533 wrapper_runtime_invoke_object_runtime_invoke_dynamic_intptr_intptr_intptr_intptr_0 (mscorlib.dll.7.s:553593)
13 TradeClient1 0x0087ade6 mono_jit_runtime_invoke (mini.c:5786)
14 TradeClient1 0x008f606a mono_runtime_invoke (object.c:2757)
15 TradeClient1 0x0094325b monotouch_trampoline (monotouch-glue.m:808)
16 UIKit 0x30e5c234 -[UIApplication _handleApplicationSuspend:eventInfo:] + 760
17 UIKit 0x30decefe -[UIApplication handleEvent:withNewEvent:] + 2094
18 UIKit 0x30dec566 -[UIApplication sendEvent:] + 54
19 UIKit 0x30debf3a _UIApplicationHandleEvent + 5826
20 GraphicsServices 0x3382e22a PurpleEventCallback + 882
22 CoreFoundation 0x370ec4c4 __CFRunLoopDoSource1 + 140
23 CoreFoundation 0x370eb312 __CFRunLoopRun + 1370
24 CoreFoundation 0x3706e4a4 CFRunLoopRunSpecific + 300
25 CoreFoundation 0x3706e36c CFRunLoopRunInMode + 104
26 GraphicsServices 0x3382d438 GSEventRunModal + 136
27 UIKit 0x30e1acd4 UIApplicationMain + 1080
28 TradeClient1 0x0058dea3 wrapper_managed_to_native_MonoTouch_UIKit_UIApplication_UIApplicationMain_int_string___intptr_intptr (monotouch.dll.7.s:184346)
29 TradeClient1 0x00531acb monotouch_MonoTouch_UIKit_UIApplication_Main_string__ (monotouch.dll.7.s:29167)
30 TradeClient1 0x0062ac43 TradeClient1_TradeClient1_Application_Main_string__ (TradeClient1.exe.7.s:25)
31 TradeClient1 0x0049b533 wrapper_runtime_invoke_object_runtime_invoke_dynamic_intptr_intptr_intptr_intptr_0 (mscorlib.dll.7.s:553593)
32 TradeClient1 0x0087ade6 mono_jit_runtime_invoke (mini.c:5786)
33 TradeClient1 0x008f606a mono_runtime_invoke (object.c:2757)
34 TradeClient1 0x008f8d4a mono_runtime_exec_main (object.c:3932)
35 TradeClient1 0x008fc69a mono_runtime_run_main (object.c:3562)
36 TradeClient1 0x0087f83a mono_jit_exec (driver.c:1122)
37 TradeClient1 0x008779e6 main (main.m:1732)
38 TradeClient1 0x00067d47 start + 39
Comment 1 Rolf Bjarne Kvinge [MSFT] 2012-05-29 06:48:04 UTC
I believe this is a problem with TestFlight - TestFlight is treating a signal as a crash before giving mono the chance to handle it properly. Can you try to reproduce this without TestFlight? That way it would be clear if it is TestFlight or not.
Comment 2 PJ 2013-11-19 17:05:28 UTC
This bug has been in the NEEDINFO state with no changes for the last 90 days. Can we put this back into the NEW or CONFIRMED state, or are we still awaiting response?

If there is no change in the status of this bug over the next two weeks, this bug will be marked as NORESPONSE.
Comment 3 PJ 2013-12-05 18:35:52 UTC
This bug has not been changed from the NEEDINFO state since my previous comment, marking as RESOLVED NORESPONSE.

Please feel free to REOPEN this bug at any time if you are still experiencing the issue. Please add the requested information and set the bug back to the NEW (or CONFIRMED) state.