Increase stack size for host when running in IIS In-Proc

[analogrelay]

Epic #8833

Blocked by https://github.com/dotnet/coreclr/issues/21450

Once there's an API/Property to increase the stack size, we need to react to it in IIS in two ways:

1. Increase the default to something more appropriate for our scenario
2. Make it configurable in web.config (if possible).

[analogrelay]

ETA of the blocking issue is preview6.

[jahanford]

@anurse can the stack size limits cause issues with the inbuilt Dependency Injection or am I more likely having a dependency recursion problem? I'm having an overflow exception only present when using InProcess hosting.

[analogrelay]

I'm not specifically aware of DI issues here, but it is certainly possible. The stack size when running in IIS is significantly smaller than when running as a standard .NET Console app. The easiest way to test is to run your app directly on Kestrel and see if you still hit the StackOverflowException. If you do, it's more likely to be a runaway recursive call, if you don't it may just be a deep stack that's hitting the IIS limit.

[jahanford]

@anurse thank you for the timely response, I have no issues when running on Kestrel, hopefully this change in 3.0 fixes it up.

[analogrelay]

Good to know! Yeah, that indicates you should have a better experience when we get this change in.

[analogrelay]

Need to review if the corefx API is present.

[martincostello]

@Projkt-James We seemed to experience the issue with 2.2.x when doing model binding, particularly when re-executing a request in an error handler.

[analogrelay]

Yep, I believe model binding can also produce fairly deep stacks. This should be improved with this coming change.