Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Triangle example has validation layer errors #113

Closed
rukai opened this issue Mar 28, 2019 · 3 comments
Closed

Triangle example has validation layer errors #113

rukai opened this issue Mar 28, 2019 · 3 comments
Assignees
Labels
type: bug Something isn't working

Comments

@rukai
Copy link
Contributor

rukai commented Mar 28, 2019

These two validation layer errors are repeatedly displayed while running the the triangle example with the latest wgpu git master.
OS: Arch Linux
GPU: GTX 960
Driver: Nvidia proprietary driver, version 418

        [0] 0x56010ba02080, type: 6, name: NULL
ERROR 2019-03-28T08:00:06Z: gfx_backend_vulkan: [Validation]  [ VUID-vkBeginCommandBuffer-commandBuffer-00049 ] Object: 0x56010ba009a0 (Type = 6) | Calling vkBeginCommandBuffer() on active command buffer 56010ba009a0 before it has completed. You must check command buffer fence before this call. The Vulkan spec states: commandBuffer must not be in the recording or pending state. (https://www.khronos.org/registry/vulkan/specs/1.1-extensions/html/vkspec.html#VUID-vkBeginCommandBuffer-commandBuffer-00049)
VUID-vkBeginCommandBuffer-commandBuffer-00049(ERROR / SPEC): msgNum: 0 - Calling vkBeginCommandBuffer() on active command buffer 56010ba009a0 before it has completed. You must check command buffer fence before this call. The Vulkan spec states: commandBuffer must not be in the recording or pending state. (https://www.khronos.org/registry/vulkan/specs/1.1-extensions/html/vkspec.html#VUID-vkBeginCommandBuffer-commandBuffer-00049)
    Objects: 1
        [0] 0x56010ba009a0, type: 6, name: NULL
ERROR 2019-03-28T08:00:06Z: gfx_backend_vulkan: [Validation]  [ VUID-vkQueueSubmit-pCommandBuffers-00071 ] Object: VK_NULL_HANDLE (Type = 6) | Command Buffer 0x56010ba009a0 is already in use and is not marked for simultaneous use. The Vulkan spec states: If any element of the pCommandBuffers member of any element of pSubmits was not recorded with the VK_COMMAND_BUFFER_USAGE_SIMULTANEOUS_USE_BIT, it must not be in the pending state. (https://www.khronos.org/registry/vulkan/specs/1.1-extensions/html/vkspec.html#VUID-vkQueueSubmit-pCommandBuffers-00071)
VUID-vkQueueSubmit-pCommandBuffers-00071(ERROR / SPEC): msgNum: 0 - Command Buffer 0x56010ba009a0 is already in use and is not marked for simultaneous use. The Vulkan spec states: If any element of the pCommandBuffers member of any element of pSubmits was not recorded with the VK_COMMAND_BUFFER_USAGE_SIMULTANEOUS_USE_BIT, it must not be in the pending state. (https://www.khronos.org/registry/vulkan/specs/1.1-extensions/html/vkspec.html#VUID-vkQueueSubmit-pCommandBuffers-00071)
    Objects: 1
@kvark kvark added the type: bug Something isn't working label Mar 28, 2019
@kvark
Copy link
Member

kvark commented Mar 28, 2019

Thank you for filing! I also do notice the errors, and they are a bit surprising since at some recent point I thought we fixed all the things :) Anyhow, this definitely needs to be investigated.

@kvark kvark added the help required We need community help to make this happen. label Mar 28, 2019
@kvark
Copy link
Member

kvark commented Mar 29, 2019

@rukai so here is a strange thing. I clearly remember fixing this, but now looking at the git history I'm not seeing the fix. So it must have been lost during numerous patches I was producing at that time. My apologies about this!

Good news is, the problem is known, and fix is trivial - will be merged as a part of #114
With this in, I can run a complex app without any per-frame validation errors 🎉

@kvark kvark self-assigned this Mar 29, 2019
@kvark kvark removed the help required We need community help to make this happen. label Mar 29, 2019
bors bot added a commit that referenced this issue Mar 31, 2019
114: [0.2] First bits of draw call validation, better submission tracking r=grovesNL a=kvark

Fixes #113 

Co-authored-by: Dzmitry Malyshau <dmalyshau@mozilla.com>
@rukai
Copy link
Contributor Author

rukai commented Apr 2, 2019

This was resolved, thanks!

@rukai rukai closed this as completed Apr 2, 2019
mitchmindtree pushed a commit to mitchmindtree/wgpu that referenced this issue Feb 23, 2020
113: build: exclude necessities for packaging, fixes gfx-rs#112 r=kvark a=m4b

I believe this is the minimal set required as an external dep, e.g., don't need tests, etc., and other folders. I can't seem to find any explicit recommendations here though: https://doc.rust-lang.org/cargo/reference/manifest.html#the-exclude-and-include-fields-optional


Co-authored-by: m4b <m4b.github.io@gmail.com>
kvark pushed a commit to kvark/wgpu that referenced this issue Jun 3, 2021
113: build: exclude necessities for packaging, fixes gfx-rs#112 r=kvark a=m4b

I believe this is the minimal set required as an external dep, e.g., don't need tests, etc., and other folders. I can't seem to find any explicit recommendations here though: https://doc.rust-lang.org/cargo/reference/manifest.html#the-exclude-and-include-fields-optional


Co-authored-by: m4b <m4b.github.io@gmail.com>
Patryk27 pushed a commit to Patryk27/wgpu that referenced this issue Nov 23, 2022
RandyMcMillan pushed a commit to RandyMcMillan/wgpu that referenced this issue Jun 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants