c# - 将 clr 更新到 4.7 后应用程序崩溃

Question

我们有一个 Windows 网络服务。三年多来一直运行良好。但是两个月前，我们安装了一台新机器和最新版本的 .NET Framework (v4.7)。我们还更新了服务中的 .NET Framework，因为我们需要新功能。

在那之后，服务开始每周崩溃一次，一周一次。

Faulting application name: Service.exe, version: 0.0.0.0, time stamp: 0x5a2e8f7a Faulting module name: clr.dll, version: 4.7.2053.0, time stamp: 0x58fa6d2a Exception code: 0xc0000005 Fault offset: 0x0000000000057947 Faulting process id: 0x704 Faulting application start time: 0x01d38529f1ad4283 Faulting application path: C:\Octopus\Applications\Service\1.0.315\Service.exe Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll Report Id: 8b138308-f165-11e7-8e89-1458d0b5ac3c

Application: Service.exe Framework Version: v4.0.30319 Description: The process was terminated due to an internal error in the .NET Runtime at IP 000007FEF9F87947 (000007FEF9F30000) with exit code 80131506.

Application: Service.exe Framework Version: v4.0.30319 Description: The process was terminated due to an internal error in the .NET Runtime at IP 000007FEF9F87947 (000007FEF9F30000) with exit code 80131506

Faulting application name: Service.exe, version: 0.0.0.0, time stamp: 0x5a2e8f7a Faulting module name: clr.dll, version: 4.7.2053.0, time stamp: 0x58fa6d2a Exception code: 0xc0000005 Fault offset: 0x00000000001bae0b Faulting process id: 0xea4 Faulting application start time: 0x01d37e14ddc4b59a Faulting application path: C:\Octopus\Applications\Service\1.0.315\Service.exe Faulting module path: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll Report Id: 8e3458e1-ecae-11e7-8e89-1458d0b5ac3c

Application: Service.exe Framework Version: v4.0.30319 Description: The process was terminated due to an internal error in the .NET Runtime at IP 000007FEFA0EAE0B (000007FEF9F30000) with exit code 80131506.

您知道为什么会发生这种情况吗？无论如何，我正在强烈考虑降级。

Answer 1

我不得不卸载 DynaTrace

以防万一你安装了这个......

https://answers.dynatrace.com/questions/190584/why-does-my-net-application-malfunction-after-upgr.html

https://answers.dynatrace.com/questions/190584/why-does-my-net-application-malfunction-after-upgr.html