runtime: Process.VirtualMemorySize64 (at least) is giving corrupt values
System.Diagnostics.Process.VirtualMemorySize64 has an unexpected High Value (Windows 10 x64)
Example:
using System;
class Program
{
static void Main(string[] args)
{
Console.WriteLine("VirtualMemorySize:{0:#,0.}", System.Diagnostics.Process.GetCurrentProcess().VirtualMemorySize64);
Console.ReadKey();
}
}
Output: VirtualMemorySize:2.199.520.038.912 Expected output : <= 150 MB as with .NET Classic
About this issue
- Original URL
- State: closed
- Created 7 years ago
- Comments: 22 (18 by maintainers)
I Think Microsoft should add a seperate new class for all performance values, which the user needs. Most wanted for me is the “commit” value. These values should be clearly defined and kept stable, even if new feutures are added. A good example for performance analysis is the vmmap.exe frome the sysinternals suite. You should be able to get exact performance analysis value from inside a .NET Core Application.