Vulkan-Samples: crash on resizing Linux Nvidia
this is not a Nvidia bug, read https://github.com/KhronosGroup/Vulkan-Samples/issues/250#issuecomment-1416238684
Vulkan SDK 1.2.131.2 Vulkan-Samples cloned and built just now Nvidia driver latest 460.39 Linux
Bug: Crash on resizing (after multiple resizes, many times resize window)
launching and resizing window
build/linux/app/bin/Release/x86_64/vulkan_samples --sample texture_loading
result
[error] [samples/api/texture_loading/texture_loading.cpp:465] Detected Vulkan error: ERROR_DEVICE_LOST
launching with VK_INSTANCE_LAYERS=VK_LAYER_KHRONOS_validation
vk_layer_settings.txt config:
khronos_validation.debug_action = VK_DBG_LAYER_ACTION_LOG_MSG
khronos_validation.report_flags = error,warn,perf
khronos_validation.log_filename = log.txt
full log log.txt
Mip errors
VUID-VkFramebufferCreateInfo-pAttachments-00882(ERROR / SPEC): msgNum: 0 - vkCreateFramebuffer(): VkFramebufferCreateInfo attachment #0 mip level 0 has dimensions smaller than the corresponding framebuffer dimensions. Here are the respective dimensions for attachment #0, framebuffer:
come without crashing just on resizing
crash is:
VUID-vkDestroyImageView-imageView-01026(ERROR / SPEC): msgNum: 0 - Cannot call vkDestroyImageView on VkImageView 0xaec0000000aec[] that is currently in use by a command buffer. The Vulkan spec states: All submitted commands that refer to imageView must have completed execution (https://www.khronos.org/registry/vulkan/specs/1.1-extensions/html/vkspec.html#VUID-vkDestroyImageView-imageView-01026)
Objects: 1
[0] 0xaec0000000aec, type: 14, name: NULL
VUID-vkDestroyImageView-imageView-01026(ERROR / SPEC): msgNum: 0 - Cannot call vkDestroyImageView on VkImageView 0xaf10000000af1[] that is currently in use by a command buffer. The Vulkan spec states: All submitted commands that refer to imageView must have completed execution (https://www.khronos.org/registry/vulkan/specs/1.1-extensions/html/vkspec.html#VUID-vkDestroyImageView-imageView-01026)
Objects: 1
[0] 0xaf10000000af1, type: 14, name: NULL
VUID-vkDestroyImage-image-01000(ERROR / SPEC): msgNum: 0 - Cannot call vkDestroyImage on VkImage 0xaef0000000aef[] that is currently in use by a command buffer. The Vulkan spec states: All submitted commands that refer to image, either directly or via a VkImageView, must have completed execution (https://www.khronos.org/registry/vulkan/specs/1.1-extensions/html/vkspec.html#VUID-vkDestroyImage-image-01000)
Objects: 1
[0] 0xaef0000000aef, type: 10, name: NULL
VUID-vkFreeMemory-memory-00677(ERROR / SPEC): msgNum: 0 - Cannot call vkFreeMemory on VkDeviceMemory 0xaf00000000af0[] that is currently in use by a command buffer. The Vulkan spec states: All submitted commands that refer to memory (via images or buffers) must have completed execution (https://www.khronos.org/registry/vulkan/specs/1.1-extensions/html/vkspec.html#VUID-vkFreeMemory-memory-00677)
Objects: 1
[0] 0xaf00000000af0, type: 8, name: NULL
VUID-vkDestroyFramebuffer-framebuffer-00892(ERROR / SPEC): msgNum: 0 - Cannot call vkDestroyFramebuffer on VkFramebuffer 0xaf20000000af2[] that is currently in use by a command buffer. The Vulkan spec states: All submitted commands that refer to framebuffer must have completed execution (https://www.khronos.org/registry/vulkan/specs/1.1-extensions/html/vkspec.html#VUID-vkDestroyFramebuffer-framebuffer-00892)
Objects: 1
[0] 0xaf20000000af2, type: 24, name: NULL
VUID-vkFreeCommandBuffers-pCommandBuffers-00047(ERROR / SPEC): msgNum: 0 - Attempt to free VkCommandBuffer 0x2619cd8[] which is in use. The Vulkan spec states: All elements of pCommandBuffers must not be in the pending state (https://www.khronos.org/registry/vulkan/specs/1.1-extensions/html/vkspec.html#VUID-vkFreeCommandBuffers-pCommandBuffers-00047)
Objects: 1
[0] 0x2619cd8, type: 6, name: NULL
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 21 (7 by maintainers)
@tgfrerer if you can send your repro app at vulkan-support@nvidia.com, I can take a look.
I’m going to reopen this as it sounds like an NVIDIA bug and it’s good to get visibility to them. I recommend reporting it to their SDK team directly.
I apologize for not saying more before; but I have been unable to reproduce this. I’ve tried both Wayland and X11 and haven’t seen the crash.