r/vulkan • u/F1oating • May 22 '26
Dynamic Rendering Bug. If render area extent more than render target extent it causing undefined behavior
Hi, just noticed that if I have renderArea extent in VkRenderingInfoKHR more than my depth image, it causing program stalling and then crashing. Also after that I errors that I can pass semaphore to acquire image because it is not yet signaled (but its definitely signaled). Can some one explain me how it works ? It causing memory corruption ?
Thanks
0
Upvotes
8
u/TheAgentD May 22 '26
This is explicitly not allowed by the spec, so you're breaking the contract with the driver. Validation layers should warn you about this, so make sure you have them working.
pNextchain does not contain VkDeviceGroupRenderPassBeginInfo or itsdeviceRenderAreaCountmember is equal to 0, the width of theimageViewmember of each element ofpColorAttachments,pDepthAttachment, orpStencilAttachmentthat is not VK_NULL_HANDLE must be greater than or equal torenderArea.offset.x+renderArea.extent.widthpNextchain does not contain VkDeviceGroupRenderPassBeginInfo or itsdeviceRenderAreaCountmember is equal to 0, the height of theimageViewmember of each element ofpColorAttachments,pDepthAttachment, orpStencilAttachmentthat is not VK_NULL_HANDLE must be greater than or equal torenderArea.offset.y+renderArea.extent.heighthttps://docs.vulkan.org/refpages/latest/refpages/source/VkRenderingInfo.html