Description

I've come across with this fatal error (supposedly being ExecutionEngineException based on Googling for that exit code) that kills process whilst testing one fairly large application that deals with large scale data processing - Event Viewer captured the following details (crash address details appear to be consistent in 3 instances of this issue:

Application: ********.exe
CoreCLR Version: 6.0.121.56705
.NET Version: 6.0.1
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 00007FF7C6613757

Application: ********.exe
CoreCLR Version: 6.0.121.56705
.NET Version: 6.0.1
Description: The process was terminated due to an internal error in the .NET Runtime.at IP 00007FF696C3917B (00007FF6969B0000) with exit code 80131506.

Reproduction Steps

Fatal error is inconsistent and application + data too large to create repro at this stage. There was a new install of .NET Desktop Runtime 6.0.1

Expected behavior

Not having fatal crash.

Actual behavior

Crashes

Regression?

No response

Known Workarounds

No response

Configuration

AMD EPYC Zen 2 server on Windows Server 2012 R2, very reliable, runs same software on .NET 4.7.1.

Other information

The following app settings were used:

  "System.IO.UseNet5CompatFileStream": true,
  "System.Runtime.TieredCompilation": true,
  "System.Runtime.TieredCompilation.QuickJit": true,
  "System.Runtime.TieredCompilation.QuickJitForLoops": true,
  "System.Globalization.UseNls": false,
  "System.GC.Server": true,
  "System.GC.Concurrent": true,
  "System.GC.CpuGroup": true,
  "System.GC.LOHThreshold": 85000,

I'll add further information as it becomes available - mostly posting now in hope that provided information will be useful and get some feedback about what can possibly be crashing inside to narrow things down