previousupnext

4.4 The Relict Heap

LeapHeap initialises early in the life of a Windows NT process, but not early enough to prevent one NT native heap, the process heap, from being created. In LeapHeap terminology this is the relict heap because it is a survivor of the early life of a NT process and not thereafter normally used. The relict heap has a few kilobytes of allocations already in it by the time LeapHeap stems the flow.

Application calls of Windows API heap routines are generally vectored to the analogous LeapHeap routine, but the relict heap may occasionally be entered: