There are other posts with problems regarding "Managed Debugging Assistant DisconnectedContext", but this one the I got is quite strange, because there's no reason why it should be triggered.
It's only a timer (with 640ms interval) that checks if the clipboard's text is empty or not. See this image: Managed Debugging Assistant Error Any ideas why it's happening? :( I tried using a try/catch block inside the timer (like a "On Error Resume Next" in VB) but it doesn't even catch the exception... weird.
[Edit] @vasily.sib didn't know the full copy-paste of the exception was needed. That's why I added a screenshot. I wouldn't do this to someone who needs help. A "please paste the full error" message would do the trick ;)
Here it is: Managed Debugging Assistant 'DisconnectedContext' : 'Transition into COM context 0x14fad18 for this RuntimeCallableWrapper failed with the following error: The requested object does not exist. (Exception from HRESULT: 0x80010114). This is typically because the COM context 0x14fad18 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.'
User contributions licensed under CC BY-SA 3.0