Crash of our NetCore 6 Application

[jogibear9988]

Description

Our Application crashed with a internal NetCore Runtime error

Name der fehlerhaften Anwendung: MCC.Common.Services.NTServiceHost.exe, Version: 6.0.0.0, Zeitstempel: 0x61954b73
Name des fehlerhaften Moduls: coreclr.dll, Version: 6.0.121.56705, Zeitstempel: 0x619543a3
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000001cd61b
ID des fehlerhaften Prozesses: 0x1c78
Startzeit der fehlerhaften Anwendung: 0x01d84e3c0e051071
Pfad der fehlerhaften Anwendung: C:\mlog\mcc\application\service\MCC.Common.Services.NTServiceHost.exe
Pfad des fehlerhaften Moduls: C:\Program Files\dotnet\shared\Microsoft.NETCore.App\6.0.1\coreclr.dll
Berichtskennung: 5c858fb-c4c0-413f-b4d9-764bff36c45e
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

Application: MCC.Common.Services.NTServiceHost.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 00007FFED781D61B (00007FFED7650000) with exit code c0000005.

Reproduction Steps

• no idee how, it did not crash every time. Only once after a few hours

Expected behavior

Application Should not crash

Actual behavior

Application crashes

Regression?

No response

Known Workarounds

No response

Configuration

No response

Other information

No response

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[danmoseley]

Hello. Are you able to get a crash dump?

[MagicAndre1981]

look if update to 6.0.4 from todays patchday helps

[danmoseley]

Saying a little more -- a crash in a .NET app is usually not caused by the runtime, but instead by unsafe code or incorrect pinvoke signatures.
Did this start crashing after a .NET update? Did it eg only crash on 6.0 but not 5.0?
If you can get a native callstack, it might suggest whether the bug is .NET or not. But the info above is not enough to tell us.

This issue has been marked needs-author-action since it may be missing important information. Please refer to our contribution guidelines for tips on how to report issues effectively.

[jogibear9988]

In Net4.8 we also sometimes had crashes cause of a error on our side with a Unmanged DLL import, but then we saw in the stacktrace where the crash came from. But also we deliverd a debug build when we used FullFramework.

Problem is, there software runs for days (it's a Warehousmanagement System), and this was the first crash, and I could not reproduce. I now enabled MemoryDumps, so hopefully if it crashes again it will be caught.

Would a debug build help, our would I not see more in the stack?

[jogibear9988]

We had the same crash again:

[jogibear9988]

I enabled crash dumps in windows registry, is a restart of the computer required to enable them?

[seayxu]

same problem
.NET Runtime 6.0.3 to 6.0.5,still exist.