Changes between Initial Version and Version 10 of Ticket #187


Ignore:
Timestamp:
Oct 4, 2022, 6:42:59 PM (19 months ago)
Author:
phosit
Comment:

The allocation profiler got removed in [26805]

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #187

    • Property Status new → closed
    • Property Milestone Beta
    • Property Resolution → wontfix

  • Ticket #187 – Description

    initial v10  
    11Currently the in-game profiler shows the number of memory allocations per frame in each profile node (at least when compiled with MSVC and the Debug CRT). It might be nice to also show the total amount of still-allocated memory that has ever been allocated under a particular node, to see which bits are responsible for using lots of memory.
    2 
    32I expect that could be done without much pain by using _CrtSetAllocHook to catch allocations and frees: allocations can be added to the count in the current profile node, and some kind of map can store the allocation request number and the current node (I'm hoping you can remember nodes like that), and frees can look up the appropriate node to subtract the size from (because we don't want to count freed memory, and because it's not necessarily going to be freed in the same place as it was allocated). That'd be a little slow, so it should be optional and disabled by default.