profiling-and-memory

Profiling & memory capture commands

Record a Profiler capture (.data) or take a memory snapshot (.snap) from a running Editor or a connected development Player. Both follow the diagnostics run_audit shape: the start command returns immediately, and you poll a *_status command until it reports completed, then read the path it gives you.

Both capture from whatever the Editor's Profiler is connected to: the same connection the Profiler window's target dropdown sets. Choose it with diagnostics profiler_connect, or leave it where it is.

unity command diagnostics profiler_targets
unity command diagnostics profiler_connect --target editor
unity command diagnostics profiler_record --frames 300
unity command diagnostics profiler_record_status

Targets

diagnostics profiler_targets

List what the Editor's Profiler can connect to: this Editor plus any connected development Players. current marks what diagnostics profiler_record and diagnostics memory_snapshot capture from.

No parameters.

Returns: object — { status, current, targets: [{ guid, name, isEditor, connectable, current, deepProfilingSupported }] }.

Notes: isEditor means this Editor process, guid -1. A connection to another Editor is an ordinary remote target. deepProfilingSupported is false for a Player built without Deep Profiling Support. A Player attached through Autoconnect Profiler does not appear in Unity's own target list, so the current connection is always listed even when Unity omits it.

diagnostics profiler_connect

Point the Editor's Profiler connection at a target, as choosing it in the Profiler window does. The connection stays there afterwards.

Parameter	Required	Default	Description
target	yes	–	editor for this Editor, or a guid or name from diagnostics profiler_targets. A name may be a unique part of one.

Returns: object — { status: "ok", target, guid, switched, message? }, or { status: "error" | "busy", message }.