Vulkan renderdoc crash, vkBindBufferMemory
Hello,
I am working on a vulkan app.
I tried taking capture on an oculus quest pro using the latest v68.16 version.
I am using raw vulkan code and I think the issue is on the libVkLayer_GLES_RenderDoc.so side.
I am using vulkan memory allocator for all my allocations:
tried multiple scenarios, this is one example of callstack:
Essentially what happens, is either vkBindBufferMemory or vkBindBufferMemory2 is intercepted by the renderdoc validation layer. The validation layer tried to inspect my buffer pointer for replayability I suppose. It ends up calling CreateAddressRange which is a nullptr.
I think everything boils down to VK_KHR_buffer_device_address, it does not appear to be supported by either my quest pro or quest3. But even if not supported, it looks like renderdoc is using some of its feature such as vkGetBufferDeviceAddress or vkGetBufferOpaqueCaptureAddress and fails to do so.
Is there any way of avoiding renderdoc to use this extension?
I ran a similar app on Quest3 and ends up with another callstack/
Looks like renderdoc is intercepting my swap chain creation and force
1000257000 -> VK_ERROR_INVALID_OPAQUE_CAPTURE_ADDRESS
VK_KHR_buffer_device_address once more which produce VK_ERROR_INVALID_OPAQUE_CAPTURE_ADDRESS
Any idea?
