The drafted setup for capturing tracking information was indeed way to elaborate. Notably I wanted to capture the actual `BuffHandle` -- and that caused a host of visibility and access problems, since that handle was meant to be used as a front-end to the BufferTracker, and only that. Now we just capture the hash-IDs and the storage size, and we do not even keep relations or record a state-ENUM; we just smash a copy of that data into a registry vector for each state separately, which allows to do a lookup, count the number of handled allocations and access the memory.
11 MiB
11 MiB
| The file is too large to be shown. |