Wgpu-rs: queue.write_buffer causes vulkan validation error about used commandbuffer

Created on 30 May 2020  路  2Comments  路  Source: gfx-rs/wgpu-rs

I've been updating from wgpu-rs from 0.5 to master. All good until I started swapping scratch buffer creation against queue.write_buffer. Doing so in my fork of imgui-wgpu-rs spams me with vulkan validation errors:

VALIDATION [VUID-vkResetCommandBuffer-commandBuffer-00045 (511214570)] : Validation Error: [ VUID-vkResetCommandBuffer-commandBuffer-00045 ] Object 0: handle = 0x2300a297780, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0x1e7883ea | Attempt to reset VkCommandBuffer 0x2300a297780[] which is in use. The Vulkan spec states: commandBuffer must not be in the pending state (https://www.khronos.org/registry/vulkan/specs/1.1-extensions/html/vkspec.html#VUID-vkResetCommandBuffer-commandBuffer-00045)
object info: (type: COMMAND_BUFFER, hndl: 2405352175488)

fairly simple change, didn't change anything around the encoders:
https://github.com/Wumpf/imgui-wgpu-rs/commit/05110e90b2efae4d606bfdab446f6e614e8ae16b#diff-b4aea3e418ccdb71239b96952d9cddb6R444-R447

To repro check out the linked commit and run cargo run --example hello_world

bug

All 2 comments

We'll fix this ASAP!

So quick! Thank you!!

Was this page helpful?
0 / 5 - 0 ratings

Related issues

sagacity picture sagacity  路  3Comments

gzp-crey picture gzp-crey  路  3Comments

imjasonmiller picture imjasonmiller  路  3Comments

m4b picture m4b  路  5Comments

donpdonp picture donpdonp  路  3Comments