Jan Kotas

This is hit intermittently on both macOS and Linux, different architectures, for different tests. I have just resolved #99885 as a duplicate. The problem seems to be a race condition...

> would it be OK to ignore "operation not permitted" errors on Kill(entireProcessTree: true)? I do not know. We need to understand what leads to the "operation not permitted" errors.

Delete workaround added in https://github.com/dotnet/runtime/pull/102958 once this gets fixed.

Managed stack: ``` 000000B5ADDBC2E8 00007ff892f1e26c [InlinedCallFrame: 000000b5addbc2e8] 000000B5ADDBC2B0 00007ff892f1e26c System.RuntimeTypeHandle.GetActivationInfo(System.RuntimeType, System.Object (Void*) ByRef, Void* ByRef, Void (System.Object) ByRef, Boolean ByRef) [/_/src/coreclr/System.Private.CoreLib/src/System/RuntimeHandles.cs @ 283] 000000B5ADDBC3C0 00007ff892f2ac2c System.RuntimeType+ActivatorCache..ctor(System.RuntimeType) [/_/src/coreclr/System.Private.CoreLib/src/System/RuntimeType.ActivatorCache.cs @ 49] 000000B5ADDBC410...

``` if (global::WinRT.ExceptionHelpers.TryHandleWinRTServerException(__this__, __exception__)) { return 0; } global::WinRT.ExceptionHelpers.SetErrorInfo(__exception__); return global::WinRT.ExceptionHelpers.GetHRForException(__exception__); ``` I assume that this block is repeated a lot. You may want to turn into an API or...

Yes, this problem still exists in current CoreRT.

It is not unusual that performance of CPU-bound microbenchmarks is sensitive to memory alignment, code alignment or other factors that results into trends like this: https://github.com/dotnet/runtime/issues/39031#issuecomment-682207270 . This can be...

Hello Christian, I am sorry, but there is not much new at this point beyond what I have said in https://github.com/dotnet/coreclr/issues/20287#issuecomment-447122236 . We definitely do want to have a great...

@charlesroddie Thank you for the feedback. We will get the status on the front page updated. > Mono has a lot of compatibility and extends the reach of .Net (into...

> crossgen? Currently it doesn't have good tooling That is getting fixed for .NET Core 3.0 (see https://github.com/dotnet/sdk/pull/2997). > At that point, aren't you basically talking about crossgen? Yep, there...