You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Native AOT applications emits some events (GCBulkNode, GCBulkEdge, GCBulkRootEdge, TypeBulkType) that are related to managed GC that can be collected via a client diagnostic tool like, dotnet-gcdump for managed heap analysis. However, since native AOT applications do not carry metadata, the type IDs require client time symbol lookup for user friendly analysis of the object graph. There is already some existing support for other similar projects that might be useful when adding support for native AOT. There are also windows specific APIs that might help.
The text was updated successfully, but these errors were encountered:
Native AOT applications emits some events (GCBulkNode, GCBulkEdge, GCBulkRootEdge, TypeBulkType) that are related to managed GC that can be collected via a client diagnostic tool like, dotnet-gcdump for managed heap analysis. However, since native AOT applications do not carry metadata, the type IDs require client time symbol lookup for user friendly analysis of the object graph. There is already some existing support for other similar projects that might be useful when adding support for native AOT. There are also windows specific APIs that might help.
The text was updated successfully, but these errors were encountered: