Profile Running Process
Run dotMemory as a standalone application. The dotMemory Home window will open.
Under Choose what you want to profile, Running Process, select the process you are going to profile. If the process you are looking for is missing, click Show All Processes to grant dotMemory administrative permissions.
Make sure the created run configuration is selected in the New Process Run list.
Under Choose how you want to profile it, specify profiling options:
Collect allocation data: choose between Sampled (approximate data on object size) and Full (accurate data on object count and size). Learn more about data collection
Optionally, if your application creates a number of processes, and you want to profile only specific ones, configure process filters.
If required, specify other profiling options.
Click Start.
Run the application you want to profile. The profiling session will start right after the profiler attaches to the application process.
- What if the profiler doesn't attach to my process?
Possible reasons:
The process you're trying to profile is not a managed process.
The profiler has attached to another managed process started in the system. Try restarting profiling, and if the problem persists, configure process filters.
Some issues are possible for processes targeting .NET 6.0 and later. If profiling doesn't start, try restarting the process and all its parent processes. For example, if you run your process from the Windows command prompt, restart both the command prompt and the process.
Go through a particular workflow in your application (if you want to check it on potential memory issues) or reproduce a particular memory issue. Collect memory snapshots using the Get Snapshot button. Learn more about how to control the profiling session
After you collect the data, either close the profiled application or detach the profiler using the Detach button.