dev-unity-profiler-mind

Use the Unity CPU Profiler to inspect method self-time rankings and look for GC.Collect in the timeline, which indicates allocations on hot paths. Eliminate per-frame new allocations by caching references, pooling objects, and pre-sizing collections.

Take a baseline snapshot at a clean state, perform the suspect action repeatedly, then take a second snapshot and compare them filtering by new objects. Object types that grow, such as Texture2D or event handlers, indicate leaks from unreleased Addressables or missing unsubscriptions.

Periodic hitches typically indicate GC allocation spikes on hot paths like Update or FixedUpdate loops. Common causes include string concatenation, boxing, FindObjectOfType calls, and unbounded collections that trigger garbage collection.

Use the C# Job System with Burst compilation for CPU-intensive per-frame loops such as pathfinding, NPC updates, or physics sampling that block the main thread. Jobs run in parallel on worker threads using NativeArray data without managed object access.

Enable Overdraw mode in the Frame Debugger to visualize transparent rendering layers, where bright spots indicate fill-rate hot spots. Fix overdraw by using opaque materials, merging UI layers into sprite atlases, and disabling bloom or distortion effects on low-end devices.