Visual Studio 2015 StandardCollector.Service.exe失控的I/O [英] Visual Studio 2015 StandardCollector.Service.exe runaway I/O

问题描述

由于StandardCollector.Service.exe导致大量I/O，Visual Studio 2015(14.0.25431.01更新3)将完全停止.调试项目可将持续200 mb/sec的数据写入temp目录.所有性能数据(etl).

Visual Studio 2015 (14.0.25431.01 Update 3) is coming to a complete halt due to massive I/O caused by the StandardCollector.Service.exe. Debugging a project results in a sustained 200 mb / sec data written in the temp directory. All performance data (etl).

内存分配正常.

此行为是新的.我使用Visual Studio 15多年来没有(但通常是这样)抱怨.

This behaviour is new. I used Visual Studio 15 for years without (but for the usual) complaints.

我找到了诊断工具.在调试时通过在工具->调试->常规->选项->启用诊断工具中禁用诊断工具可以解决I/O问题.但是，由于我依赖此功能，因此这不是永久解决方案.

I tracked it down to the Diagnostic Tools. Disabling Diagnostic Tools in Tool -> Debugging -> General -> Options -> Enable Diagnostic Tools while debugging solves the I/O problem. However this is not a permanent solution since I rely on this feature.

问:在调试时启用诊断工具时，导致大量I/O的原因是什么?

Q: What causes the massive I/O when Enable Diagnostic Tools while debugging is switched on?

推荐答案

免责声明:我在Visual Studio上工作，特别是在诊断工具上

Disclaimer: I work on Visual Studio, specifically the Diagnostic Tools

您已启用CPU使用率工具，该工具是使用Windows事件跟踪(ETW)的事件探查器.基本上，它每毫秒收集一次CPU堆栈，并且该信息已写入ETL文件中，我们可以从中分析和显示性能信息.无论是否在调试会话之间将其打开，我们都会坚持下去，尤其是可以将其打开，重新启动调试和配置文件应用程序启动.我们最大的问题之一是，它很容易开启和忘记.

You have the CPU Usage tool enabled which is a profiler that uses event tracing for windows (ETW). Basically it is collecting a CPU stack every millisecond and that information is getting written to an ETL file that we analyze and display performance information from. We persist whether or not you turned it on between debug sessions, specifically so that you can turn it on, restart debugging, and profile app startup. One of our biggest issues is that it is easy to turn on and forget.

要关闭此功能，请切换到诊断工具中的"CPU使用率"选项卡，然后按启用CPU收集"按钮(文本因VS版本而异).上面的CPU图形应​​从绿色切换为蓝色，表明它已关闭.另外，在最新版本的Visual Studio中，我们添加了资源限制，如果系统上的磁盘或内存使用率太低(当启用并忘记了CPU工具时，这种情况很常见)将禁用诊断工具.

To turn it off, switch to the CPU Usage tab in the Diagnostic Tools and press the "Enable CPU Collection" button (text is different based on VS version). The CPU graph above should switch from green to blue indicating that it has been turned off. Also, in the latest version of Visual Studio we have added resource limits which will disable the diagnostic tools if the disk or memory usage on the system gets too low, which was common when the CPU tool was enabled and forgotten about.

这篇关于Visual Studio 2015 StandardCollector.Service.exe失控的I/O的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！