.Net 4.0 Windows 应用程序在 Windows Server 2008 下的 clr.dll 中崩溃 [英] .Net 4.0 Windows Application crashes in clr.dll under Windows Server 2008

问题描述

我有一个 Windows 应用程序计划每天运行，但根据 EventViewer 中的以下日志间歇性地失败.

I have a Windows application scheduled to run on a daily basis and fails intermittently as per the following log in EventViewer.

Faulting application name: MyApplication.exe, version: 1.0.0.0, time stamp: 0x4d54829a
Faulting module name: clr.dll, version: 4.0.30319.1, time stamp: 0x4ba21eeb
Exception code: 0xc0000005
Fault offset: 0x00000000000029e1
Faulting process id: 0xbb1c
Faulting application start time: 0x01cbd99223d8b4eb
Faulting application path: E:MyApplicationMyApplication.exe
Faulting module path: C:WindowsMicrosoft.NETFramework64v4.0.30319clr.dll
Report Id: 7e74ec7e-45a5-11e0-a95d-003048de380d

在第二个 EventViewer 日志中显示:

And in the second EventViewer log it says:

The process was terminated due to an internal error in the .NET Runtime at IP 000007FEF97329E1 (000007FEF9730000) with exit code 80131506.

服务器是 Win Server 2008 R2，应用程序使用 .Net 4.0(您也可以在错误日志中看到).

The server is Win Server 2008 R2 and the application uses .Net 4.0 (as you can see in the error log too).

应用程序密集使用多线程，从远程数据库读取并写入本地硬盘.

The application uses multi-threading intensively and reads from a remote database and writes to local hard disk.

对导致此问题的原因有任何猜测以及有关如何调查的任何建议?我不知道它在大约 5-10 小时的应用程序生命周期中哪里失败了.

Any guesses on what causes this issue and any suggestions on how to investigate? I have no idea where it fails in the life of the application which is about 5-10 hours.

推荐答案

热修复大部分都消失了，我遇到了类似的问题，所以我会在这里分享我的答案.

The hot-fix has mostly vanished and I faced a similar issue, so I'll share my answer here.

我的解决方案围绕着我将 Lamda 传递给 P/Invoke 的事实:

My solution revolved around the fact that I was passing a Lamda to a P/Invoke:

https://stackoverflow.com/a/52360307/4700841

这篇关于.Net 4.0 Windows 应用程序在 Windows Server 2008 下的 clr.dll 中崩溃的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！