Jan Kotas

CoreRT libraries are not unloadable. There are number of problems that would need to be fixed to make them unload cleanly. https://github.com/dotnet/corert/pull/7011#issuecomment-519403322 lists some of the issues.

Preventing the library from unloading is the only reliable way.

cc @JulieLeeMSFT This issue is not diagnosable because of missing crash dump.

The only thing missing for background GC should be the changes in the write barrier helper. You may also need to add this to InlinedBulkWriteBarrier in C++ runtime code. It...

The GC should have a good idea about the sections that are committed already. Can this be fixed by fixing the ranges that the GC is passing into the virtual...

It is best to submit GC fixes to dotnet/runtime repo, and get better testing and review from GC experts there.

This is failing because of https://github.com/dotnet/corert/pull/8143 is just a skeleton without actual implementation. The skeleton has to be filled in with actual implementation to make this work. https://github.com/dotnet/corert/pull/8143#issuecomment-626201188 has some...

> https://github.com/dprint/dprint-plugin-roslyn/tree/corert Roslyn has infinite recursive expansion around `Microsoft.CodeAnalysis.VisualBasic.TypeArgumentInference.StronglyConnectedComponent`. This is #363. If you see the compiler not making progress and consuming a lot of memory, it is pretty much...

> The proposed alternative here seems to be something like the following instead: The proposed alternative here is the following structure instead: ``` +---linux-x64 | \---native | +---linux-musl-x64 | |...

The assumption in this proposal is that it is just about glibc vs. musl for the vast majority of native libraries bundled into packages. The Python solution is based on...