You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently MemoryDiagnoser via GcStats uses GC.GetAllocatedBytesForCurrentThread on .NET Core to get the number of allocated bytes, but that ends up yielding misleading information for async tests or tests that otherwise involve work being performed on multiple threads. .NET Core 3.0 adds GC.GetTotalAllocatedBytes: https://github.com/dotnet/corefx/blob/5310b5646aa1c8b18b6546dc5980c30c35d5f4e4/src/System.Runtime/ref/System.Runtime.cs#L1276
It'd be great to use that instead when it's detected to be available.
The text was updated successfully, but these errors were encountered:
Currently MemoryDiagnoser via GcStats uses GC.GetAllocatedBytesForCurrentThread on .NET Core to get the number of allocated bytes, but that ends up yielding misleading information for async tests or tests that otherwise involve work being performed on multiple threads. .NET Core 3.0 adds GC.GetTotalAllocatedBytes:
https://github.com/dotnet/corefx/blob/5310b5646aa1c8b18b6546dc5980c30c35d5f4e4/src/System.Runtime/ref/System.Runtime.cs#L1276
It'd be great to use that instead when it's detected to be available.
The text was updated successfully, but these errors were encountered: