C Specification

To destroy a VkPipelineBinaryKHR, call:

// Provided by VK_KHR_pipeline_binary
void vkDestroyPipelineBinaryKHR(
    VkDevice                                    device,
    VkPipelineBinaryKHR                         pipelineBinary,
    const VkAllocationCallbacks*                pAllocator);

Parameters

  • device is the logical device that created the pipeline binary object.

  • pipelineBinary is the handle of the pipeline binary object to destroy.

  • pAllocator controls host memory allocation as described in the Memory Allocation chapter.

Description

Valid Usage
  • VUID-vkDestroyPipelineBinaryKHR-pipelineBinary-09614
    If VkAllocationCallbacks were provided when pipelineBinary was created, a compatible set of callbacks must be provided here

  • VUID-vkDestroyPipelineBinaryKHR-pipelineBinary-09615
    If no VkAllocationCallbacks were provided when pipelineBinary was created, pAllocator must be NULL

Valid Usage (Implicit)
  • VUID-vkDestroyPipelineBinaryKHR-device-parameter
    device must be a valid VkDevice handle

  • VUID-vkDestroyPipelineBinaryKHR-pipelineBinary-parameter
    If pipelineBinary is not VK_NULL_HANDLE, pipelineBinary must be a valid VkPipelineBinaryKHR handle

  • VUID-vkDestroyPipelineBinaryKHR-pAllocator-parameter
    If pAllocator is not NULL, pAllocator must be a valid pointer to a valid VkAllocationCallbacks structure

  • VUID-vkDestroyPipelineBinaryKHR-pipelineBinary-parent
    If pipelineBinary is a valid handle, it must have been created, allocated, or retrieved from device

Host Synchronization
  • Host access to pipelineBinary must be externally synchronized

See Also

Document Notes

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.

Copyright 2014-2025 The Khronos Group Inc.

SPDX-License-Identifier: CC-BY-4.0