Update the doc about System.Diagnostics.Process regarding dotnet runtime issue 97132

Author: Wenbo

xml/System.Diagnostics/Process.xml

@@ -112,6 +112,11 @@
 
  A system process is uniquely identified on the system by its process identifier. Like many Windows resources, a process is also identified by its handle, which might not be unique on the computer. A handle is the generic term for an identifier of a resource. The operating system persists the process handle, which is accessed through the <xref:System.Diagnostics.Process.Handle%2A> property of the <xref:System.Diagnostics.Process> component, even when the process has exited. Thus, you can get the process's administrative information, such as the <xref:System.Diagnostics.Process.ExitCode%2A> (usually either zero for success or a nonzero error code) and the <xref:System.Diagnostics.Process.ExitTime%2A>. Handles are an extremely valuable resource, so leaking handles is more virulent than leaking memory.
 
+ In the MacOS, the following properties will return 0:
+ - <xref:System.Diagnostics.Process.peakvirtualmemorysize64?displayProperty=nameWithType>
+ - <xref:System.Diagnostics.Process.PrivateMemorySize64?displayProperty=nameWithType>
+ - <xref:System.Diagnostics.Process.PeakWorkingSet64?displayProperty=nameWithType>
+
 > [!NOTE]
 >  This class contains a link demand and an inheritance demand at the class level that applies to all members. A <xref:System.Security.SecurityException> is thrown when either the immediate caller or the derived class does not have full-trust permission. For details about security demands, see [Link Demands](/dotnet/framework/misc/link-demands).