 Important: |
|---|
| This is retired content. This content is outdated and is no longer being maintained. It is provided as a courtesy for individuals who are still using these technologies. This content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
This function returns the size, in bytes, of a memory block allocated from a heap by the HeapAllocor HeapReAllocfunction.
DWORD HeapSize( HANDLE hHeap , DWORD dwFlags , LPCVOID lpMem );
Parameters
- hHeap
- [in] Handle to the heap in which the memory block resides. This handle is returned by the HeapCreateor GetProcessHeapfunction.
- dwFlags
- [in] Specifies several controllable aspects of accessing the
memory block. Only one flag is currently defined; however, all
other flag values are reserved for future use. Specifying this flag
will override the corresponding flag specified in the
flOptionsparameter when the heap was created using the
HeapCreatefunction.
Value Description HEAP_NO_SERIALIZE Specifies that mutual exclusion will not be used while HeapSizeis accessing the heap. This flag should not be specified when accessing the process heap. The system may create additional threads within the application's process that simultaneously access the process heap. - lpMem
- [in] Pointer to the memory block whose size the function will
obtain. This is a pointer returned by the
HeapAllocor
HeapReAllocfunction.
Return Values
The size, in bytes, of the allocated memory block indicates success. 0xFFFFFFFF indicates failure. The function does not call SetLastError. An application cannot call GetLastErrorfor extended error information.
Remarks
Serialization ensures mutual exclusion when two or more threads attempt to simultaneously allocate or free blocks from the same heap. There is a small performance cost to serialization, but it must be used whenever multiple threads allocate and free memory from the same heap. Setting the HEAP_NO_SERIALIZE flag eliminates mutual exclusion on the heap. Without serialization, two or more threads that use the same heap handle might attempt to allocate or free memory simultaneously, likely causing corruption in the heap. The HEAP_NO_SERIALIZE flag can, therefore, be safely used only in the following situations:
- The process has only one thread.
- The process has multiple threads, but only one thread calls the heap functions for a specific heap.
- The process has multiple threads, and the application provides
its own mechanism for mutual exclusion to a specific heap.
Requirements
Runs on Versions Defined in Include Link to Windows CE OS 1.0 and later Winbase.h Lmem.lib Note This API is part of the complete Windows CE OS package as provided by Microsoft. The functionality of a particular platform is determined by the original equipment manufacturer (OEM) and some devices may not support this API.
See Also
GetLastError, GetProcessHeap, HeapAlloc, HeapCreate, HeapDestroy, HeapFree, HeapReAlloc, SetLastError