Unity has the following tools to keep track of memory allocations:
To track garbage collection allocations with the CPU Usage Profiler module, perform the following steps:
The GC.Alloc column displays the number of bytes that Unity allocated on the managed heap for the selected frame and thread.
Allocations can occur on all threads so you might want to use the thread selection drop down to check out other threads than the main thread. You can also use the Timeline view and keep an eye out for the GC.Alloc
samples, which are colored bright magenta.
Tip: Use the Call Stacks mode to enable the full call stack traces for GC.Alloc
samples. Call stacks give you precise details of where the garbage collector made the allocation without needing to use Deep Profiling mode, which might impact performance.
You can use the Memory Profiler module to track garbage collection memory allocations, but it only provides a high-level overview of where Unity allocated memory. For detailed information on memory usage in your application, use the Memory Profiler package.
To track garbage collection memory allocations with the Memory Profiler module, perform the following steps:
The Managed Heap statistic displays the amount of memory that the garbage collector managed, and it includes memory that Unity might have allocated and reused in subsequent frames. This means that the sum of the GC.Alloc
samples over all frames doesn’t total how much the managed memory grew in that time.
The GC allocated in frame statistic diplays the amount of memory that was allocated in this frame. This amount might be higher than the CPU Usage module displays in the GC.Alloc column of the Hierarchy view. This is because the GC.Alloc
statistic includes allocations made across all threads and also within Editor only samples, or as part of the EditorLoop
. The Hierarchy view only displays one thread at a time and hides the allocations made in Editor only samples by default and collapses the code running as part of the EditorLoop
unless the profiler targets the Editor and not Play mode.
Important: To get the most accurate information, profile your application on a development buildA development build includes debug symbols and enables the Profiler. More info
See in Glossary on the target platform or device you want to build to. The Unity Editor works in a different way to a build, and this affects the profiling data. For example, the GetComponent
method always allocates memory when it’s executed in the Editor, but not in a built project.
Did you find this page useful? Please give it a rating:
Thanks for rating this page!
What kind of problem would you like to report?
Thanks for letting us know! This page has been marked for review based on your feedback.
If you have time, you can provide more information to help us fix the problem faster.
Provide more information
You've told us this page needs code samples. If you'd like to help us further, you could provide a code sample, or tell us about what kind of code sample you'd like to see:
You've told us there are code samples on this page which don't work. If you know how to fix it, or have something better we could use instead, please let us know:
You've told us there is information missing from this page. Please tell us more about what's missing:
You've told us there is incorrect information on this page. If you know what we should change to make it correct, please tell us:
You've told us this page has unclear or confusing information. Please tell us more about what you found unclear or confusing, or let us know how we could make it clearer:
You've told us there is a spelling or grammar error on this page. Please tell us what's wrong:
You've told us this page has a problem. Please tell us more about what's wrong:
Thank you for helping to make the Unity documentation better!
Your feedback has been submitted as a ticket for our documentation team to review.
We are not able to reply to every ticket submitted.