class in UnityEditor.Profiling.Memory.Experimental
包含类型描述条目的类,从 PackedMemorySnapshot.typeDescriptions 返回。
assembly | 此类型加载自的程序集的名称。 |
baseOrElementTypeIndex | 此类型的基本类型,由编入 PackedMemorySnapshot.typeDescriptions 的索引指向该类型。 |
fieldIndices | 包含索引(指向此类型所有字段的描述)的数组,可从 PackedMemorySnapshot.fieldDescriptions 访问。 |
flags | 为此类型描述设置的标志,用于定义此类型是数组还是值类型,以及类型的数组秩。 |
size | 此类型实例的大小(以字节为单位)。如果此类型为数组类型,则该属性描述了数组中的单个元素将占用的字节数。 |
staticFieldBytes | 在创建快照时,存储此类型静态字段的字节的实际内容。 |
typeDescriptionName | 此类型的名称。 |
typeIndex | 此类型的类型索引。此索引是一个编入 PackedMemorySnapshot.typeDescriptions 数组的索引。 |
typeInfoAddress | 包含虚拟机内此类型描述的内存中地址。该属性可用于将堆中的托管对象与其对应的 TypeDescription 相匹配,因为托管对象的第一个指针指向其类型描述。 |
GetNumEntries | 类型描述条目的数量。 |
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.