.NET Core process crashes after upgrading to Hangfire 1.7.2

[wangjia184]

My project is a .NET Core self-hosted(non-IIS, run as windows service) application which has been using hangfire since 1.6.X. And we keep upgrading hangfire assemblies from NuGet whenever there are new releases.

However, since Hangfire 1.7.1, my application crashes after several hours running. If I downgrade hangfire to v1.7.0, everything is fine.

Version	Result
1.7.0	Stable
1.7.1	Crashed after several hours
1.7.2	Crashed after several hours

The process crashes and it can't be handled/caught by managed code. From Windows Event Viewer, we can see error as below.

Faulting application name: Service.exe, version: 0.0.0.0, time stamp: 0x5c65fa1e
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc00000fd
Fault offset: 0x00007ffee3e12308
Faulting process id: 0x7ac
Faulting application start time: 0x01d4ff1a20acbf34
Faulting application path: C:\Service\Service.exe
Faulting module path: unknown
Report Id: 1fe5e02f-6bce-11e9-80da-915397a8f6e4
Faulting package full name: 
Faulting package-relative application ID: 

The exception code 0xc00000fd means stack overflow.

[odinserj]

Hm, thanks for the detailed description, so we should track the method that cause the exception now. Could you capture a memory dump for example as written here https://blogs.msdn.microsoft.com/amb/2011/12/02/how-to-configure-debug-diagnostic-to-capture-stack-overflow-exceptions/ ?

[Svisstack]

1.7.2 crashes all the time - thanks for the information that 1.7.0 is stable. I'm currently checking that information.

Unfortunately don't have logs.

[Svisstack]

1.7.0 is also not stable for me, I downgraded to 1.6.25 and checking that - in a few days I could have logs.

[odinserj]

Please add more information regarding this topic – logs, stack traces, dumps, configuration logic, etc. I'm still unable to reproduce the issue.