Recursive client code (Stack Overflow) causes stateless service to crash without any sensible error or exception

[esbenbach]

Describe the bug
Given a stateless .NET 6 service with a recursion bug, service fabric seems to do "something" causing the service to crash and get restarted without any sensible error reporting.

Attaching the debugger shows an "Access Violation" message in the output, but no sane amount of toggling exception options on gives information about the underlying "StackOverflowException".

To Reproduce
Create a simple stateless service and cause a recursion bug.
An minimal reproduction is attached with a console app that behaves correctly using the same "buggy code".

AccessViolationIssue.zip

Expected behavior
Some indication of the underlying exception should be provided in logs, events or whatever.

[esbenbach]

poke anyone?