# DisconnectedContext causes crash **URL:** \ **Category:** Windows\ **Created:** [August 5, 2021, 10:41pm UTC](https://devforum.zoom.us/t/disconnectedcontext-causes-crash/55314 "2021-08-05T22:41:32Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![brandon1](https://avatars.discourse-cdn.com/v4/letter/b/ea666f/32.png) [@brandon1](https://devforum.zoom.us/u/brandon1)\ **Post date:** [August 5, 2021, 10:41pm UTC](https://devforum.zoom.us/t/disconnectedcontext-causes-crash/55314/1 "2021-08-05T22:41:32Z")
**Description** Application crash due to the below error, reproduced in a modified version of the demo application. The Demo application is modified for expediency with a pre-filled auth token and user login. The error occurs intermittently, on my system is somewhere less than 1 in 15 attempts to get it to reproduce. Using LoginParam4Email to login. Am starting a meeting using the following: StartParam userType=SDK\_UT\_NORMALUSER and NormalUserStart = StartParam4NormalUser {isVideoOff =true, isAudioOff = false, isDirectShareDesktop = false} Error occurs immediately after using the End Meeting For All button. I have also added the stack track that ends up in Event Viewer. **Which Desktop Client SDK version?** C# Wrapper 5.5.12511.0422 **To Reproduce(If applicable)** Steps to reproduce the behavior: 1. Rundemo Exe 2. Authenticate 3. Login 4. Start meeting 5. Without any other interaction with Zoom Window , End → End Meeting For All. 6. Repeat steps 5,6 until application crashes. **Screenshots** If applicable, add screenshots to help explain your problem. **Device (please complete the following information):** Windows 10 Pro 10.0.19043 **Additional context** **Error seen from Visual Studio** Managed Debugging Assistant ‘DisconnectedContext’ : ‘Transition into COM context 0x14e7e28 for this RuntimeCallableWrapper failed with the following error: The object invoked has disconnected from its clients. (Exception from HRESULT: 0x80010108 (RPC\_E\_DISCONNECTED)). This is typically because the COM context 0x14e7e28 where this RuntimeCallableWrapper was created has been disconnected or it is busy doing something else and cannot process the context transition. No proxy will be used to service the request on the COM component and calls will be made to the COM component directly. This may cause corruption or data loss. To avoid this problem, please ensure that all COM contexts/apartments/threads stay alive and are available for context transition, until the application is completely done with the RuntimeCallableWrappers that represents COM components that live inside them.’ **Second Error in Event Viewer** Faulting application name: zoom\_sdk\_demo.exe, version: 1.0.0.0, time stamp: 0x610c66b8 Faulting module name: KERNELBASE.dll, version: 10.0.19041.1151, time stamp: 0x5da51925 Exception code: 0xe0434352 Fault offset: 0x0012b512 Faulting process id: 0x12e5c Faulting application start time: 0x01d78a499d6f89d2 Faulting application path: C:\Users\User\Downloads\zoom-c-sharp-wrapper-5.5.12511.0422\zoom-c-sharp-wrapper-5.5.12511.0422\bin\zoom\_sdk\_demo.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report Id: d69559ee-29c8-4488-b0c6-1714a25158f1 Faulting package full name: Faulting package-relative application ID: **First Error in Event Viewer** Application: zoom\_sdk\_demo.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.InvalidCastException at System.StubHelpers.InterfaceMarshaler.ConvertToNative(System.Object, IntPtr, IntPtr, Int32) at MS.Win32.UnsafeNativeMethods+ITfThreadMgr.SetFocus(ITfDocumentMgr) at System.Windows.Input.InputMethod.EnableOrDisableInputMethod(Boolean) at System.Windows.Input.TextServicesManager.Focus(System.Windows.DependencyObject) at System.Windows.Input.KeyboardDevice.ChangeFocus(System.Windows.DependencyObject, Int32) at System.Windows.Input.KeyboardDevice.TryChangeFocus(System.Windows.DependencyObject, System.Windows.Input.IKeyboardInputProvider, Boolean, Boolean, Boolean) at System.Windows.Input.KeyboardDevice.Focus(System.Windows.DependencyObject, Boolean, Boolean, Boolean) at System.Windows.Input.KeyboardDevice.Focus(System.Windows.IInputElement) at System.Windows.Interop.HwndKeyboardInputProvider.OnSetFocus(IntPtr) at System.Windows.Interop.HwndKeyboardInputProvider.FilterMessage(IntPtr, MS.Internal.Interop.WindowMessage, IntPtr, IntPtr, Boolean ByRef) at System.Windows.Interop.HwndSource.InputFilterMessage(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) ---
**Author:** ![Michael\_Condon](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael_condon/32/13543_2.png) [@Michael\_Condon](https://devforum.zoom.us/u/Michael_Condon)\ **Post date:** [August 6, 2021, 9:51pm UTC](https://devforum.zoom.us/t/disconnectedcontext-causes-crash/55314/2 "2021-08-06T21:51:31Z")
Hey @brandon1, Thanks for using the dev forum! Are you seeing this in the C++ demo app as well? Thanks! Michael ---
**Author:** ![brandon1](https://avatars.discourse-cdn.com/v4/letter/b/ea666f/32.png) [@brandon1](https://devforum.zoom.us/u/brandon1)\ **Post date:** [August 9, 2021, 3:37pm UTC](https://devforum.zoom.us/t/disconnectedcontext-causes-crash/55314/3 "2021-08-09T15:37:50Z")
I don’t know about it reproducing with C++. I haven’t set it up with the C++ SDK. ---
**Author:** ![Michael\_Condon](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael_condon/32/13543_2.png) [@Michael\_Condon](https://devforum.zoom.us/u/Michael_Condon)\ **Post date:** [August 9, 2021, 7:42pm UTC](https://devforum.zoom.us/t/disconnectedcontext-causes-crash/55314/4 "2021-08-09T19:42:38Z")
Hey @brandon1, I understand. We do not provide much developer support for the C# wrapper as it is not actively maintained by Zoom. Thanks! Michael ---
**Author:** ![don\_ucw](https://avatars.discourse-cdn.com/v4/letter/d/6bbea6/32.png) [@don\_ucw](https://devforum.zoom.us/u/don_ucw)\ **Post date:** [August 10, 2021, 4:33pm UTC](https://devforum.zoom.us/t/disconnectedcontext-causes-crash/55314/5 "2021-08-10T16:33:17Z")
Hi Michael, until we ramp up with a C++ developer to support us - can you please investigate on your end? We specifically purchased a zoom business license to get development support with the Zoom SDK and the Zoom C# wrapper, this is the first we have heard that you do not support it. thanks Don ---
**Author:** ![Michael\_Condon](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/michael_condon/32/13543_2.png) [@Michael\_Condon](https://devforum.zoom.us/u/Michael_Condon)\ **Post date:** [August 10, 2021, 9:10pm UTC](https://devforum.zoom.us/t/disconnectedcontext-causes-crash/55314/6 "2021-08-10T21:10:55Z")
Hey @don_ucw, It is difficult to investigate C# wrapper issues, as sometimes the issue is caused by something outside of the SDK itself. If you’d like, you can send me a dump file and your SDK logs to [developersupport@zoom.us](mailto:developersupport@zoom.us) and I can forward them to the engineers. However, if the issue is with the wrapper itself, it would have to be modified locally on your end. Thanks! Michael ---
**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\ **Post date:** [September 10, 2021, 7:11am UTC](https://devforum.zoom.us/t/disconnectedcontext-causes-crash/55314/7 "2021-09-10T07:11:22Z")
Closed on September 10, 2021, 7:11am UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.