Development environment:
- Windows 10 in Parallels Desktop
- Visual Studio 15.6
Scene restoration:
Use Visual Studio 15.6 (ie Visual Studio 2017) to create a new ASP.NET Core MVC project, start debugging, and prompt:
调试器的工作进程（msvsmon.exe）意外退出。调试将终止In fact, this problem has been encountered many times, but it has not been recorded, which leads to the search for a solution every time.
Open the "Event Viewer", click "Windows Logs" - "Application" in turn, you can see two "Error" level logs:
Among them, the log with the source "Application Error" is displayed as follows:
描述:
错误应用程序名称: msvsmon.exe，版本: 15.0.27428.2043，时间戳: 0x5adf7e7a
错误模块名称: unknown，版本: 0.0.0.0，时间戳: 0x00000000
异常代码: 0xc0000005
错误偏移量: 0x0000000000000000
错误进程 ID: 0x1518
错误应用程序启动时间: 0x01d3de90a8d1c526
错误应用程序路径: C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\Common7\IDE\Remote Debugger\x64\msvsmon.exe
错误模块路径: unknownThe log with source "Visual Studio Remote Debugger" shows the following:
描述:
无法找到来自源 Visual Studio Remote Debugger 的事件 ID 1002 的描述。本地计算机上未安装引发此事件的组件，或者安装已损坏。可以安装或修复本地计算机上的组件。
如果该事件产生于另一台计算机，则必须在该事件中保存显示信息。
以下是包含在事件中的信息:
远程调试器遇到了严重的内部错误，必须中止远程调试会话。请重新启动调试。Then Google came to this article Annoying Visual Studio 2010 Crash Restart Problem , after seeing that the author finally closed the firewall to solve the problem, I immediately tried to close the firewall and retry, and sure enough, the debugger started normally.
Then I thought, I built NGINX on Windows Server last night, but I encountered a problem that the external network could not be accessed. The reason was that there was no list to be ngingx.exeadded to in the firewall settings 允许应用通过防火墙进行通信.
Thinking of this, I reopened the firewall, then msvsmon.exeadded to 允许应用通过防火墙进行通信the list, and checked 专用and 公用.
Start debugging again, success!
Look carefully at msvsmon.exethe path, under Remote Debuggerthe folder, does it mean remote debugging? So you need to communicate with the external network through the firewall?
We know that vs can remotely debug the code of another machine, but local debugging should not involve external network communication. Does it have something to do with my virtual machine environment? But it has also been encountered in non-VM environments before.
I hope that friends who understand can clarify!
UPDATE :
The solution above, it only worked once, then the second time it didn't work...
No way, continue to find a solution, try to use English keyword Google
the debugger's worker process (msvsmon.exe) unexpectedly exited. debugging will be aborted
to find this article msvsmon.exe crashed when debugging , summarizes a lot of solutions to this problem, one of which caught my attention:
I too have Astrill installed. Completely uninstalling Astrill fixed the issue.Yes! I just installed Astrill, and my heart burst with joy, it turned out to be caused by this guy!
After uninstalling Astrill and restarting the computer, there is no problem with repeated startup and debugging, perfect!