`vkResetCommandPool` seems to slow down overtime and eats up memory

Gaming and Visualization Technologies APIs Vulkan
1

I made a minimum case to reproduce the bug (on latest NVIDIA drivers and latest Vulkan SDK. Windows 11 with latest updates. I can reproduce the bug on both RTX3090 and RTX3080).

The program call vkResetCommandPool to release command buffers created for previous frames. This should be equivalent to freeing all command buffers / recreate the command pool again. However, calling vkResetCommandPool does not seem to be taking effect.
The memory consumption increases a few hundred KB each frame, and the program significantly slows down after a few thousand frames. Memory consumption can grow over 10G after a few minumtes for some applications.

ebce6befa05ea30c9b6cb64af0d598bf
ebce6befa05ea30c9b6cb64af0d598bf808×233 4.4 KB

7f8fad06672edc91151d052b37d5f6f0
7f8fad06672edc91151d052b37d5f6f0644×359 17.2 KB

Switching to recreating the command pool each frame, or free command buffers after use seems fine.

2

Ok, more discoveries here.

Seems that destroying the command buffer pool and recreate it again does handle some of the unlimited memory growth. However, when recording vkCmdTraceRaysIndirect and vkCmdBuildAccelerationStructure commands, unlimited memory growth appeared again. So the only safe way seems to be freeing the command buffer explicitly. This bug had haunted me for weeks. I hope it will be fixed soon.