Memory Profiler 模块
有两种方法可以在 Unity 中分析应用程序的内存使用情况：
- Memory Profiler module: A built-in Profiler module that gives you basic information on where your application uses memory.
- Memory Profiler package: A Unity package that you can add to your project. It adds an additional Memory Profiler window to the Unity Editor, which you can then use to analyze memory usage in your application in even more detail. You can store and compare snapshots to find memory leaks, or see the memory layout to find memory fragmentation issues.
本页涵盖有关内置 Memory Profiler 模块的信息。有关 Memory Profiler 包的更多信息，请参阅 Memory Profiler 文档。
The Memory Profiler module visualizes counters that represent the total allocated memory in your application. You can use the memory module to see information like the number of loaded objects, and the memory that they take in total per category. You can also see the number of GC allocations per Profiler frame.
Memory profiling in the Editor
When you profile your application in the Editor, the Memory Profiler module reports higher data use than a similar profile of the application built on a target device would. This is because the Unity Editor uses specific objects that take up memory, and the Editor window itself uses extra memory.
Part of the extra memory use is because Unity treats objects like textures as read/write enabled in the Editor and keeps an extra copy of each texture on the CPU. This effectively doubles the reported memory use of textures in the Editor; for a more accurate idea of memory use by textures, profile a built version of your application running on the target platform.
Also, because Unity can’t cleanly separate the memory that the Profiler itself takes up from the Play mode’s memory, memory that the Profiler uses is displayed in the Profiler window. To remind you of this, a warning displays at the top of the Memory Profiler module details pane whenever you have the Profiler target set to Play Mode or Editor. For more precise numbers and memory usage for your application, you should profile your application on the target device and operating system you intend it to run on. For more information, see the documentation on Profiling your application.
图表类别
The Memory Profiler module is divided into categories that display detailed information on where your application spends memory. You can also click a category’s colored legend to toggle its display.
| 类别 | 描述 |
|---|---|
| Total Allocated | 应用程序已使用的内存总量。 |
| Texture Memory | 应用程序中的纹理已使用的内存量。 |
| Mesh Memory | 应用程序中的网格已使用的内存量。 |
| Material Count | 应用程序中的材质实例数量。 |
| Object Count | 应用程序中的原生对象实例数量。 |
| GC Used Memory | The amount of memory the GC heap has used. |
| GC Allocated in Frame | GC 堆中每帧分配的内存量。 |
模块详细信息面板
There are two views available in the module details pane, located at the bottom of the Profiler window:
- Simple: Displays a high level overview of the memory statistics per frame
- Detailed: Captures a memory snapshot which contains more details on the memory that native objects used, including native references to them, and Unity’s different subsystems.
To change the view, select it from the dropdown in the top left of the module details pane.
Simple 视图
The Simple view displays an overview of how Unity uses memory in real-time on a per-frame basis. It breaks down the total memory that your application uses into a few major categories. The Total value is based on the System Used Memory Profiler counter, which indicates how much memory the operating system (OS) reports as being in use by your application.
Unity sets some memory pools aside for allocations to avoid asking the operating system for memory too often. The Profiler module displays how much memory Unity reserves, and how much memory Unity used at the time of the Profiler capture.
The Simple view displays the data collected within the System Used Memory Profiler counter. This indicates how much memory the operating system (OS) reports as being in use by the app and corresponds to the Total value of the Total Committed Memory bar and the Total Memory Breakdown bar.
On platforms that support getting the total memory size of the application from the operating system, the System Memory Usage is over 0 and is the same size in a task manager.
The following reference table describes the statistics available in the Simple view, plus its corresponding profiler counter, and availability in Release builds. This information is also available via the ProfilerRecorder API and in the Profiler Module Editor so you can add them to a custom Profiler module.
| 属性 | 描述 | Corresponding Profiler counter | Available in Release Players? |
|---|---|---|---|
| Normalized | Enable this setting to scale the Total Committed Memory and Total Memory Breakdown charts to the memory usage of the selected frame. If you disable this setting, the charts scale to the total used memory within the frame range. This setting can help you see how the total or relative amounts of memory change from frame to frame | 无 | 无 |
| Total Committed Memory | The length of the Total Committed Memory bar indicates the total amount of memory that Unity’s Memory Manager system tracked, how much of that it used, and how much memory isn’t tracked through this system. | System Used Memory | 是 |
| Tracked Memory (in use / Reserved) | Indicates the total amount of memory that Unity uses and tracks (in use), and the amount of memory that Unity reserves for tracking purposes and pool allocations (Reserved). | Total Used Memory Total Reserved Memory |
是 |
| Untracked Memory | Indicates the total amount of memory that Unity used but isn’t aware of. Some examples of untracked memory are: - Memory allocated through native plug-ins or some drivers - Mono or IL2CPP type metadata - Memory that executable code and DLLs use The Memory Profiler package and native platform providers might have more information on some of these untracked memory amounts. |
无 | 无 |
| Total Memory Breakdown | Displays the same total amount as the Total Committed Memory bar but breaks it into some high level categories, based on which subsystems Unity allocated the memory for. Not all memory systems use pools or differentiate between used and reserved memory. Those that do display two numbers, the used and the reserved amount of memory. If the used amount doesn’t share the same unit (B, MB, GB) as the reserved amount, Unity displays the unit, otherwise it’s omitted. |
System Used Memory | 是 |
| Managed Heap (in use / Reserved) | The used heap size and total heap size that managed code uses. This memory is garbage collected. | GC Used Memory GC Reserved Memory |
是 |
| Graphics & Graphics Driver | 驱动程序对纹理、渲染目标、着色器和网格数据使用的估计内存量。 | Gfx Used Memory Gfx Reserved Memory |
否 |
| Audio | 音频系统的估计内存使用量。 | Audio Used Memory Audio Reserved Memory |
是 |
| Video | The Video system’s estimated memory usage. | Video Used Memory Video Reserved Memory |
是 |
| Other | Displays native memory that Unity tracks, but isn’t reported under a specific counter. To get more information on the makeup of this or the other categories, take a snapshot in the Detailed view or with the Memory Profiler package. Important: The Other category doesn’t directly map to the Other group in the Detailed view. In this view, Other contains the remainder of the native memory that was not used for the GPU side of graphics memory, the Profiler, Audio, or Video memory. |
无 | 无 |
| Profiler | The memory that the Profiler functionality uses and reserves from the system. | Profiler Used Memory Profiler Reserved Memory |
是 |
| Objects stats | Displays the amount of object instances of the types of Assets that commonly take up a high percentage of the memory (Textures, Meshes, Materials, Animation Clips), together with their accumulated sizes in memory (Assets, GameObjects, Scene Objects). Note: Texture and Mesh memory doesn’t map directly to the Graphics & Graphics Driver stat in the Total Memory Breakdown view. This is because some of that memory might also fall into the Other category of the Total Memory Breakdown bar. |
Object Count | 否 |
| Textures | 已加载的纹理总数及其使用的内存。 | Texture Count Texture Memory |
否 |
| 网格 | 已加载的网格总数及其使用的内存。 | Mesh Count Mesh Memory |
否 |
| 材质 | 已加载的材质总数及其使用的内存。 | Material Count Material Memory |
否 |
| 动画剪辑 | 已加载的动画剪辑总数及其使用的内存。 | AnimationClip Count AnimationClip Memory |
否 |
| Assets | 已加载的资源总数。 | Asset Count | 否 |
| Game Objects | The total number of GameObject instances in the scene. | GameObject Count | 否 |
| Scene Objects | The total number of dynamic UnityEngine.Objects. This number includes the GameObject Count, plus the total number of components, and everything which isn’t an asset in the scene. |
Scene Object Count | 否 |
| GC allocated in frame | Displays the amount of managed allocations in the selected frame, and their total size in bytes. | GC Allocation In Frame Count GC Allocated In Frame |
否 |
播放器中的可用性
You can use the ProfilerRecorder API to access the Memory Profiler module’s counters in Players. The following example contains a simple script that collects Total Reserved Memory, GC Reserved Memory and System Used Memory metrics, and displays those as a GUI.TextArea. The Memory Profiler module information belongs to the ProfilerCategory.Memory Profiler category.
using System.Text;
using Unity.Profiling;
using UnityEngine;
public class MemoryStatsScript : MonoBehaviour
{
string statsText;
ProfilerRecorder totalReservedMemoryRecorder;
ProfilerRecorder gcReservedMemoryRecorder;
ProfilerRecorder systemUsedMemoryRecorder;
void OnEnable()
{
totalReservedMemoryRecorder = ProfilerRecorder.StartNew(ProfilerCategory.Memory, "Total Reserved Memory");
gcReservedMemoryRecorder = ProfilerRecorder.StartNew(ProfilerCategory.Memory, "GC Reserved Memory");
systemUsedMemoryRecorder = ProfilerRecorder.StartNew(ProfilerCategory.Memory, "System Used Memory");
}
void OnDisable()
{
totalReservedMemoryRecorder.Dispose();
gcReservedMemoryRecorder.Dispose();
systemUsedMemoryRecorder.Dispose();
}
void Update()
{
var sb = new StringBuilder(500);
if (totalReservedMemoryRecorder.Valid)
sb.AppendLine($"Total Reserved Memory: {totalReservedMemoryRecorder.LastValue}");
if (gcReservedMemoryRecorder.Valid)
sb.AppendLine($"GC Reserved Memory: {gcReservedMemoryRecorder.LastValue}");
if (systemUsedMemoryRecorder.Valid)
sb.AppendLine($"System Used Memory: {systemUsedMemoryRecorder.LastValue}");
statsText = sb.ToString();
}
void OnGUI()
{
GUI.TextArea(new Rect(10, 30, 250, 50), statsText);
}
}
以下屏幕截图显示了将脚本添加到 Tanks! 教程项目的结果。
This information is available in Release Players, as are the other high level counters in the table above. If you want to see the selected memory counters in a custom module in the Profiler window, use the Module Editor to configure the chart.
Detailed 视图
The Detailed view provides a snapshot of your application’s current state. Select the Take Sample button to capture detailed memory usage for the current target. It takes the Profiler time to get this data, so the Detailed view doesn’t give you real-time details. After the Profiler takes a sample, the Profiler window displays a list view where you can explore your application’s memory usage in more detail.
Enable the Gather Object References setting at the top of the module details pane to collect information about what’s referencing an object at the time of the snapshot. The Profiler displays this information in the right-hand pane of the window.
列表视图将使用内存的对象将分为以下类别：
- Other：资源、游戏对象或组件以外的对象。其中包括诸如 Unity 用于不同系统的内存之类的信息。
- Not Saved: Objects marked as DontSave
- Builtin Resources: Unity Editor resources or Unity default resources, such as Shaders you have added to the Always Included Shaders list of the Graphics settings.
- Assets：从用户或原生代码引用的资源。
- Scene Memory: Objects and attached components.
When you click on a GameObject in the Assets or Scene Memory list, Unity highlights it in the Project or Scene view.
Note: In the Other category, memory reported under System.ExecutableAndDlls is read-only memory. The operating system might discard these pages as needed and later reload them from the file system. This generates lower memory usage, and doesn’t directly contribute to the operating system’s decision to close your application if it uses too much memory. Some of these pages might also be shared with other applications that are using the same frameworks.