vsjitdebugger.exe(Visual Studio调试器)-在生产服务器的任务管理器中显示很多 [英] vsjitdebugger.exe (Visual Studio Debugger) - shows up lots in my task manager in production server

查看:194
本文介绍了vsjitdebugger.exe(Visual Studio调试器)-在生产服务器的任务管理器中显示很多的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一个在IIS上运行的.net网站.每隔几天,我查看任务管理器,并打开10-15个vsjitdebugger.exe进程.每个人都会绑一些连接,因此除非我手动进入并结束该过程,否则它会导致数据库池出现问题.

I've got a .net web site which runs on IIS. Once every few days I look at the task manager and I've got 10-15 vsjitdebugger.exe processes open. Each one ties up some connections so it causes problems with the db pool unless I manually go in and end the process.

有一次,尽管此后已将其卸载,但Visual Studio已安装在此框中.我想知道这是否是调试器在发生错误时尝试启动的原因.

At one point, Visual Studio was installed on this box, though it's since been uninstalled. I'm wondering if this is the reason the debugger tries to start when an error occurs.

但是,我想知道的是如何在发生错误时如何使IIS停止尝试启动调试器?无论如何,它可以在不尝试调试的情况下继续生存吗?

However, what I want to know is how do I get IIS to stop attempting to launch the debugger when an error happens? Is there anyway that it can simply go on with life without trying to debug?

我还想知道,应用程序的部署方式(作为具有PDB而不是发行版的调试应用程序)会有所不同吗?甚至在web.config中打开调试功能?

I also wonder, could the way the app is deployed (as a debugged app with the PDB's instead of a release version) make a difference? Or even having debugging turned on in the web.config?

推荐答案

听起来好像机器已配置为如果进程中发生未处理的异常,则自动运行调试器.您不希望在生产服务器中使用它,而可能希望它终止该过程.此行为由注册表中的DbgManagedDebugger项控制.这是该键的文档

It sounds like the machine is configured to automatically run the debugger if an unhandled exception occurs in the process. You don't want this in a production server but instead likely want it to terminate the process. This behavior is controlled by the DbgManagedDebugger key in the registry. Here is the documentation for that key

这篇关于vsjitdebugger.exe(Visual Studio调试器)-在生产服务器的任务管理器中显示很多的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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