Managed Debugging Assistant 'ContextSwitchDeadlock' : 'The CLR has been unable to transition from COM context 0x28ab560 to COM context 0x28ab4a8 for 60 seconds. 

Managed Debugging Assistant 'ContextSwitchDeadlock' : 'The CLR has been unable to transition from COM context 0x28ab560 to COM context 0x28ab4a8 for
 60 seconds. The thread that owns the destination context/apartment is most likely either doing a non pumping wait or processing a 
very long running operation without pumping Windows messages. This situation generally has a negative performance impact and may even lead to 
the application becoming non responsive or memory usage accumulating continually over time. To avoid this problem, all single threaded apartment 
(STA) threads should use pumping wait primitives (such as CoWaitForMultipleHandles) and routinely pump messages during long running operations.'
复制代码
One fix for the problem is to go to the Debug -> Exceptions -> Managed Debug Assistants menu in Visual Studio and uncheck the ContextSwitchDeadlock

From http://blog.wpfwonderland.com/2007/08/16/clr-has-been-unable-to-transition-from-com-context-for-60-seconds/

Update2. Visual Studio 2019+:

Debug -> Windows -> Exception settings

Uncheck ContextSwitchDeadlock
复制代码

 

posted @   FredGrit  阅读(8)  评论(0)  编辑  收藏  举报
相关博文：
·  WPF The calling thread cannot access this object because a different thread owns it.
·  C# Parallel foreach Parallel Source array was not long enough. Check srcIndex and length, Destination array was not long enough. Check destIndex and length, and the array's lower bounds
·  托管调试助手 "ContextSwitchDeadlock":“CLR 无法从 COM 上下文 0xac89c0 转换为 COM 上下文 0xac8908，这种状态已持续 60 秒
·  vs2019托管调试助手 "ContextSwitchDeadlock"错误
·  托管调试助手 "ContextSwitchDeadlock"Message=托管调试助手 "ContextSwitchDeadlock":“CLR 无法从 COM 上下文 0x1b5452d0 转换为 COM 上下文 0x1b5451a8，这种状态已持续 60 秒。
阅读排行：
· 分享一个免费、快速、无限量使用的满血 DeepSeek R1 模型，支持深度思考和联网搜索！
· 基于 Docker 搭建 FRP 内网穿透开源项目（很简单哒）
· ollama系列01：轻松3步本地部署deepseek，普通电脑可用
· 25岁的心里话
· 按钮权限的设计及实现
点击右上角即可分享
微信分享提示
SQL AI 助手