Skip to content

Update the doc for System.Diagnostics.Process #9624

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Sep 22, 2025
Merged

Update the doc for System.Diagnostics.Process #9624

Changes from 4 commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
e610875
Update the doc about System.Diagnostics.Process regarding dotnet runt…
Feb 18, 2024
2f5d3ca
Try to fix some warnings from github with the previous change
Feb 21, 2024
f44bec3
Update Process.xml to fix a warning
yahoo0742 Feb 21, 2024
a215863
Try to fix some warnings from github with the previous change
Feb 22, 2024
61409a3
Update xml/System.Diagnostics/Process.xml
gewarren Sep 22, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions xml/System.Diagnostics/Process.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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>
- <xref:System.Diagnostics.Process.PrivateMemorySize64>
- <xref:System.Diagnostics.Process.PeakWorkingSet64>

> [!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).

Expand Down