I know for a fact this is the only place in the entire program that can allocate memory repeatedly. I am noticing that over time (20 minutes) my program increasingly becomes slower until it eventually crashes. Renderdoc seems to suggest I run out of device host memory. I am noticing, using nvidia-smi that my program consumes progressively more vram from 325 MiB to 327 MiB it's a small amount but it;s very conistent.
If I comment out that loop the rest of the program renders fine, never gets slower and renderdoc never complains about memory running out.
This code is alsoa port from a C++ codebase that uses VMA and the error does not seem to happen there. All of the above leads me to suspect there might be an issue with gpu-allocator.
OS: ubuntu 22.04 GPU: Nivida Gtx 1070 API: Vulkan, through ash bindings gpu-allocator version: "0.18.0"
It is hard for me to say with 100% confidence, but I think there might be a bug inside gpu-allocator causing memleaks.
I have a vulkan program which is allocating and releasing resources in a loop. Said loop looks like this:
Where:
I know for a fact this is the only place in the entire program that can allocate memory repeatedly. I am noticing that over time (20 minutes) my program increasingly becomes slower until it eventually crashes. Renderdoc seems to suggest I run out of device host memory. I am noticing, using nvidia-smi that my program consumes progressively more vram from 325 MiB to 327 MiB it's a small amount but it;s very conistent.
If I comment out that loop the rest of the program renders fine, never gets slower and renderdoc never complains about memory running out.
This code is alsoa port from a C++ codebase that uses VMA and the error does not seem to happen there. All of the above leads me to suspect there might be an issue with gpu-allocator.