Tagging subscribers to this area: @dotnet/gc
See info in area-owners.md if you want to be subscribed.

so there is no way to specify a hard limit on 32-bit? Has that always been the case?

so there is no way to specify a hard limit on 32-bit? Has that always been the case?

Yes, we should not have a heap_hard_limit for 32-bit. In fact, we asserted that fact at the beginning of gc_heap::virtual_commit.

The error #85757 also happens when deploying as self-contained to Azure App Service with win-x86 (which is selected by default in Visual Studio publish profile when you select self-contained).
Self-contained must be used to include .NET 8 Preview 4 runtime with the app because it is not availble in the Azure App Service machine out of the box.

In my case, it was Blazor Server app.

And interestingly, I cannot select x64:

So I had to create a new app service on Linux x64 which does not have available free tier (F1) (only S1).

The error #85757 also happens when deploying as self-contained to Azure App Service with win-x86 ...

@janseris, is there something you want us to help you with? This bug is already fixed and merged into the main branch, it will be available in the next preview.