Visual Studio 2017调试错误:为防止在评估函数* .toString时允许安全运行的所有线程时发生不安全中止 [英] Visual Studio 2017 Debug Error: To prevent an unsafe abort when evaluating the function *.toString all threads where allowed to run

查看:1950
本文介绍了Visual Studio 2017调试错误:为防止在评估函数* .toString时允许安全运行的所有线程时发生不安全中止的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我将Visual Studio 2017更新为版本15.8.2.

I updated Visual Studio 2017 to version 15.8.2.

此更新之后,我开始在调试时遇到这些错误:

After this update, I started to encounter these errors while debugging:

以下是错误消息:

Visual Studio调试错误:为了防止在评估函数* .toString允许运行的所有线程时发生不安全的中止.这可能会更改进程的状态,并且遇到的任何断点都将被跳过.

Visual Studio Debug Error: To prevent an unsafe abort when evaluating the function *.toString all threads where allowed to run. This may have changed the state of the process and any breakpoints encountered have been skipped.

此错误经常出现,并且一段时间后Visual Studio崩溃.

This error shows up quite often, and after a while Visual Studio crashes.

我尝试再次卸载并安装Visual Studio并重置首选项,但是我没有运气.

I tried to uninstall and install Visual Studio again and reset preferences, but I had no luck.

当我禁用选项:启用属性评估和其他隐式函数调用"时,当我尝试通过将鼠标移到某些属性上来评估某些属性时,会遇到相同的错误.如果没有它,调试起来将非常困难,在此构建之前我没有任何问题.

When I disable the option: "Enable property evaluation and other implicit function calls", I get the same error when I try to evaluate some properties by moving the mouse over them. It's quite difficult to debug without it, and I had no problems before this build.

问题与C#和Visual Basic(.NET)相同.

The problem is the same with C# and Visual Basic (.NET).

是否有针对此问题的修复程序?我的团队使用Visual Studio 2017 15.7.4版在同一个项目上工作没有问题

Is there any fix for this problem? My team has no problem working on the same project with Visual Studio 2017 version 15.7.4

推荐答案

我添加了相同的错误消息,但函数名称不同:

I add the same error message but with a different function name :

为防止在评估该功能时发生不安全的中止 'Microsoft.VisualStudio.Debugger.Runtime.Tracing.Refresh'所有线程 被允许运行.这可能已经改变了过程的状态 并且遇到的任何断点都将被跳过.

To prevent an unsafe abort when evaluating the function 'Microsoft.VisualStudio.Debugger.Runtime.Tracing.Refresh' all threads were allowed to run. This may have changed the state of the process and any breakpoints encountered have been skipped.


这就是我摆脱这个讨厌的bug的方式:
在Visual Studio 2017中转到
工具→选项→调试→常规→选中使用托管的兼容模式"
感谢这篇文章:
https://www.codeart.dk/blog/2018/9/vs2017-debugger-timeout/


This is how I got rid of this pesky bug :
In Visual Studio 2017 go to
Tools → Options → Debugging → General → Check 'Use Managed Compatibility Mode'
thanks to this article :
https://www.codeart.dk/blog/2018/9/vs2017-debugger-timeout/

这篇关于Visual Studio 2017调试错误:为防止在评估函数* .toString时允许安全运行的所有线程时发生不安全中止的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆