{"id":6059,"date":"2023-03-13T17:16:47","date_gmt":"2023-03-14T00:16:47","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/pix\/?p=6059"},"modified":"2023-03-15T09:47:32","modified_gmt":"2023-03-15T16:47:32","slug":"memory-profiling-support-for-allocations-made-from-a-titles-custom-allocator","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/pix\/memory-profiling-support-for-allocations-made-from-a-titles-custom-allocator\/","title":{"rendered":"Memory profiling support for allocations made from a title’s custom allocator"},"content":{"rendered":"

Starting with the 2303.02 release of PIX on Windows<\/a>, PIX timing captures<\/a> can track memory allocations and frees made by your custom memory allocators.<\/span><\/p>\n

By calling the new APIs, PIXRecordMemoryAllocationEvent and PIXRecordMemoryFreeEvent, you provide PIX with the data it needs to display information about all memory allocations and frees made from within your title\u2019s custom memory allocators. The data shown for your custom allocators is the same as the data shown for allocations made using either VirtualAlloc or HeapAlloc.<\/p>\n

PIXRecordMemoryAllocationEvent and PIXRecordMemoryFreeEvent are available in version 1.0.230302001 or later of the WinPIXEventRuntime<\/a>.<\/p>\n

To call PIXRecordMemoryAllocationEvent and PIXRecordMemoryFreeEvent, include pix3.h in your source code, and ensure that USE_PIX is defined. Call the APIs as shown in the following example.<\/p>\n

#include “pix3.h”<\/span><\/p>\n

void* TitleAllocate(size_t size, UINT64 metadata)<\/span><\/p>\n

{<\/span><\/p>\n

\u00a0 \u00a0 void *pAddress = layer_allocate(size);<\/span><\/p>\n

\u00a0 \u00a0 if (pAddress == NULL)<\/span><\/p>\n

\u00a0 \u00a0 \u00a0 \u00a0 return NULL;<\/span><\/p>\n

\u00a0 \u00a0 PIXRecordMemoryAllocationEvent(TITLE_ALLOCATOR, pAddress, size, <\/span><\/p>\n

\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0metadata);<\/span><\/p>\n

\u00a0 \u00a0 return pAddress;<\/span><\/p>\n

}<\/span><\/p>\n

 <\/p>\n

void TitleFree(void* baseAddress, size_t size, UINT64 metadata)<\/span><\/p>\n

{<\/span><\/p>\n

\u00a0 \u00a0 layer_free(baseAddress, 0);<\/span><\/p>\n

\u00a0 \u00a0 PIXRecordMemoryFreeEvent(TITLE_ALLOCATOR, baseAddress, size, <\/span><\/p>\n

\u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0metadata);<\/span><\/p>\n

}<\/span><\/p>\n

To see memory events corresponding to your calls to PIXRecordMemoryAllocationEvent and PIXRecordMemoryFreeEvent, select the Custom Allocator events<\/strong> check box before starting a timing capture:<\/p>\n

\"Image<\/a><\/p>\n

 <\/p>\n

PIX displays information about your custom allocations and frees alongside the data for other allocation types in the Range Details<\/strong> view of timing captures.\u00a0 Custom allocator events are grouped by allocator and shown under the Title Allocators by Id<\/strong> node.\u00a0 The allocator id is the first parameter to PIXRecordMemoryAllocationEvent.\u00a0 Note that the last parameter to PIXRecordMemoryAllocationEvent, the metadata parameter, is currently not displayed in PIX.<\/p>\n

 <\/p>\n

\"Image<\/a><\/p>\n

See Analyzing Memory usage and performance<\/a> for more details on the memory profiling features in Timing Captures.<\/p>\n

As always, please keep sending feedback and bug requests our way using the feedback button in the upper right corner of the PIX UI.<\/p>\n

Steven.<\/p>\n","protected":false},"excerpt":{"rendered":"

Starting with the 2303.02 release of PIX on Windows, PIX timing captures can track memory allocations and frees made by your custom memory allocators. By calling the new APIs, PIXRecordMemoryAllocationEvent and PIXRecordMemoryFreeEvent, you provide PIX with the data it needs to display information about all memory allocations and frees made from within your title\u2019s custom […]<\/p>\n","protected":false},"author":1915,"featured_media":6063,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-6059","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-pix"],"acf":[],"blog_post_summary":"

Starting with the 2303.02 release of PIX on Windows, PIX timing captures can track memory allocations and frees made by your custom memory allocators. By calling the new APIs, PIXRecordMemoryAllocationEvent and PIXRecordMemoryFreeEvent, you provide PIX with the data it needs to display information about all memory allocations and frees made from within your title\u2019s custom […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/pix\/wp-json\/wp\/v2\/posts\/6059","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/pix\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/pix\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/pix\/wp-json\/wp\/v2\/users\/1915"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/pix\/wp-json\/wp\/v2\/comments?post=6059"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/pix\/wp-json\/wp\/v2\/posts\/6059\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/pix\/wp-json\/wp\/v2\/media\/6063"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/pix\/wp-json\/wp\/v2\/media?parent=6059"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/pix\/wp-json\/wp\/v2\/categories?post=6059"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/pix\/wp-json\/wp\/v2\/tags?post=6059"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}