To allocate memory objects, call:
// Provided by VK_VERSION_1_0
const VkMemoryAllocateInfo* pAllocateInfo,
const VkAllocationCallbacks* pAllocator,
deviceis the logical device that owns the memory.
pAllocateInfois a pointer to a VkMemoryAllocateInfo structure describing parameters of the allocation. A successfully returned allocation must use the requested parameters — no substitution is permitted by the implementation.
pAllocatorcontrols host memory allocation as described in the Memory Allocation chapter.
pMemoryis a pointer to a VkDeviceMemory handle in which information about the allocated memory is returned.
Allocations returned by
vkAllocateMemory are guaranteed to meet any
alignment requirement of the implementation.
For example, if an implementation requires 128 byte alignment for images and
64 byte alignment for buffers, the device memory returned through this
mechanism would be 128-byte aligned.
This ensures that applications can correctly suballocate objects of
different types (with potentially different alignment requirements) in the
same memory object.
When memory is allocated, its contents are undefined with the following constraint:
The contents of unprotected memory must not be a function of the contents of data protected memory objects, even if those memory objects were previously freed.
The contents of memory allocated by one application should not be a function of data from protected memory objects of another application, even if those memory objects were previously freed.
The maximum number of valid memory allocations that can exist
simultaneously within a VkDevice may be restricted by implementation-
or platform-dependent limits.
feature describes the number of allocations that can exist simultaneously
before encountering these internal limits.
Many protected memory implementations involve complex hardware and system
software support, and often have additional and much lower limits on the
number of simultaneous protected memory allocations (from memory types with
Some platforms may have a limit on the maximum size of a single allocation.
For example, certain systems may fail to create allocations with a size
greater than or equal to 4GB.
Such a limit is implementation-dependent, and if such a failure occurs then
VK_ERROR_OUT_OF_DEVICE_MEMORY must be returned.
vkAllocateMemory must not return
For more information, see the Vulkan Specification
This page is extracted from the Vulkan Specification. Fixes and changes should be made to the Specification, not directly.