{"id":2585,"date":"2017-03-08T22:39:00","date_gmt":"2017-03-08T22:39:00","guid":{"rendered":"https:\/\/blogs.msdn.microsoft.com\/pix\/?page_id=2585"},"modified":"2017-03-08T22:39:00","modified_gmt":"2017-03-08T22:39:00","slug":"data-type-tracking-in-memory-allocation-captures","status":"publish","type":"page","link":"https:\/\/devblogs.microsoft.com\/pix\/data-type-tracking-in-memory-allocation-captures\/","title":{"rendered":"Data Type Tracking in Memory Allocation Captures"},"content":{"rendered":"

The PIX memory profiler will show data type information for heap allocations when it is available. Type information will be available if the following two conditions are met:<\/p>\n

    \n
  1. The function that allocated the type has been decorated with __declspec(allocator)<\/li>\n
  2. PIX can find your title\u2019s PDB.<\/li>\n<\/ol>\n

    The memory allocation routines in the default heap are already decorated with __declspec(allocator) so unless you have custom memory allocation routines, there is no other work you\u2019ll need to do related to __declspec(allocator).\u00a0 If your heap allocations are coming from somewhere other than the default heap, see the blog post on tracking custom allocations <\/a>for instructions on how to use __declspec(allocator).<\/p>\n

    The “Setting PDB Paths” section of the Function Summary Capture <\/a>page provides instructions for configuring PIX to find your title\u2019s PDBs.\u00a0 Briefly, if you\u2019re profiling on the same machine you just built your title on, the path to the PDB that the compiler stored in your title\u2019s modules is typically all PIX needs to locate the PDB.\u00a0 Otherwise, there are options on the Settings page to point PIX at your PDBs.<\/p>\n

    Type information is shown in two places in a memory capture.\u00a0 First, the event list on the Events tab has a column called Type Name in which the name of the allocated type is displayed.\u00a0 PIX will only be able to display the type name if the allocation routine was decorated with __declspec(allocator) as described above.<\/p>\n

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

    The second place that type information is displayed is on the Allocated Types tab.\u00a0 Statistics are provided for every type that was allocated while the capture was running.\u00a0 These statistics include the size of the type, the amount of padding in the type’s definition, the number of instances of the type that were allocated and the total number of bytes those allocations took up in the heap.<\/p>\n

    Clicking on a column sorts the event list based on the data in the column.\u00a0 Sorting can quickly help you see things like which types were allocated most frequently, which types have the most padding and so on.<\/p>\n

    Selecting a row in the event list populates the Type Info view with details of the type’s layout.\u00a0 The Type Info view will show you the offset and size of each field in the type.\u00a0 Nested types can be expanded and collapsed.\u00a0 The layout also tells you exactly where the padding sits within your type information.\u00a0 This padding information helps you determine whether your layout can be optimized to reduce wasted space.<\/p>\n

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

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

    The PIX memory profiler will show data type information for heap allocations when it is available. Type information will be available if the following two conditions are met: The function that allocated the type has been decorated with __declspec(allocator) PIX can find your title\u2019s PDB. The memory allocation routines in the default heap are already […]<\/p>\n","protected":false},"author":1915,"featured_media":4769,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_acf_changed":false,"footnotes":""},"class_list":["post-2585","page","type-page","status-publish","has-post-thumbnail","hentry"],"acf":[],"_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/pix\/wp-json\/wp\/v2\/pages\/2585","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/pix\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/pix\/wp-json\/wp\/v2\/types\/page"}],"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=2585"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/pix\/wp-json\/wp\/v2\/pages\/2585\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/pix\/wp-json\/wp\/v2\/media\/4769"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/pix\/wp-json\/wp\/v2\/media?parent=2585"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}