[Vulkan] Memory management and object sharing issues

1）Call vkCmdCopyBufferToImage with error
validation layer: vkCmdCopyBufferToImage(): VkBuffer object 0x2f0 used with no memory bound. Memory should be bound by calling vkBindBufferMemory(). The Vulkan spec states: If srcBuffer is non-sparse then it must be bound completely and contiguously to a single VkDeviceMemory object (https://www.khronos.org/registry/vulkan/specs/1.1-extensions/html/vkspec.html#VUID-vkCmdCopyBufferToImage-srcBuffer-00176)
validation layer: vkCmdCopyBufferToImage(): VkBuffer object 0x2f0 used with no memory bound. Memory should be bound by calling vkBindBufferMemory(). The Vulkan spec states: If srcBuffer is non-sparse then it must be bound completely and contiguously to a single VkDeviceMemory object (https://www.khronos.org/registry/vulkan/specs/1.1-extensions/html/vkspec.html#VUID-vkCmdCopyBufferToImage-srcBuffer-00176)
validation layer: THREADING ERROR : object of type VkBuffer is simultaneously used in thread 0x4a70 and thread 0x5ec4
validation layer: THREADING ERROR : object of type VkBuffer is simultaneously used in thread 0x4a70 and thread 0x5ec4

2）Call vkBindBufferMemory with error
validation layer: In vkBindBufferMemory(), attempting to bind memory (0x55ce) to object (0x55cb) which has already been bound to mem object 0x55cc. The Vulkan spec states: buffer must not already be backed by a memory object (https://www.khronos.org/registry/vulkan/specs/1.1-extensions/html/vkspec.html#VUID-vkBindBufferMemory-buffer-01029)
validation layer: In vkBindBufferMemory(), attempting to bind memory (0x55ce) to object (0x55cb) which has already been bound to mem object 0x55cc. The Vulkan spec states: buffer must not already be backed by a memory object (https://www.khronos.org/registry/vulkan/specs/1.1-extensions/html/vkspec.html#VUID-vkBindBufferMemory-buffer-01029)
validation layer: THREADING ERROR : object of type VkBuffer is simultaneously used in thread 0x5cac and thread 0x3b04
validation layer: THREADING ERROR : object of type VkBuffer is simultaneously used in thread 0x5cac and thread 0x3b04

Start by reproducing the reported validation errors around vkCmdCopyBufferToImage and vkBindBufferMemory. Trace the VkBuffer creation, memory binding, and concurrent use paths, then verify that buffers are bound once before use and are not accessed simultaneously across threads; the issue provides no file or test entry point.