On Tue Nov 7 15:14:50 2023 +0000, Alex Henrie wrote:
That's an interesting point. These values are presumably supposed to be freed with NsiFreeTable, but the caller could try to free them with HeapFree instead. Is there any good way to tell which allocation function Windows is internally using here?
Quick test shows that HeapSize() does return reasonable values for those allocations.