Workflow: How to capture a memory snapshot
- Open the Memory Profiler.
- Decide which target to profile, e.g., the Editor itself or a running Player (either on your local machine or on a connected device).
- In the Memory Profiler window, click the Attach drop-down menu and select the target to profile.
- Click the Capture button at the top of the Memory Profiler. The snapshot will appear on the left side of the Memory Profiler window in the Workbench panel.
Note: The Capture button will be labeled Capture Editor when the Memory Profiler is targeting the Editor, and the Editor is not in Play Mode. In that case, it will capture the Editor. If the target is a built Player or the Editor in Play Mode, it will be labeled Capture Player. Capturing a snapshot of the Editor while in Play Mode will include any memory used by the Editor as well. Memory usage in a Play Mode player is not representative of the memory usage on a device. It is always recommended to capture snapshots from a built Player on the targeted platform.
You can also trigger a memory snapshot at any moment you decide, without any interaction with the Memory Profiler window. Use the Memory Profiler Scripting API to set up capture logic in a script inside your Player. For information about custom MetaData collection, see Add Player hook.