Closed yowl closed 3 months ago
To complete the breadcrumbs here I'm following up on Zulip
(thanks for opening the issue here though!)
I believe this has since been resolved so I'm going to close, but let me know if there's still lingering issues.
Due to
cabi_realloc
being used from class constructors at initialization, there is a chicken and egg problem when initialising the dotnet runtime. Ifcabi_realloc
is implemented in managed code, the dotnet runtime must be initialised first, however the class ctors for wasi_snapshot_preview1 also want to callcabi_realloc
resulting in the following stack and crashPossibly
memory.grow
can be used instead (which is the idea behind solving the same problem but for the stack allocation)