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

Vulkan error flood on 2d bloom example #8684

Closed
Azorlogh opened this issue May 25, 2023 · 7 comments
Closed

Vulkan error flood on 2d bloom example #8684

Azorlogh opened this issue May 25, 2023 · 7 comments
Labels
A-Rendering Drawing game state to the screen C-Bug An unexpected or incorrect behavior S-Needs-Investigation This issue requires detective work to figure out what's going wrong

Comments

@Azorlogh
Copy link
Contributor

Bevy version

Tested with bevy 0.10.1 and also commit bc9144b

[Optional] Relevant system information

OS: Arch linux 6.3.1-zen
Vulkan instance version: 1.3.246

Adapter:
AdapterInfo { name: "NVIDIA GeForce RTX 2060", vendor: 4318, device: 7817, device_type: DiscreteGpu, driver: "NVIDIA", driver_info: "530.41.03", backend: Vulkan }

What you did

Ran the 2d bloom example

What went wrong

The following error floods the console endlessly:

2023-05-25T21:58:32.096948Z ERROR wgpu_hal::vulkan::instance: VALIDATION [VUID-vkCmdEndDebugUtilsLabelEXT-commandBuffer-01912 (0x56146426)]
    Validation Error: [ VUID-vkCmdEndDebugUtilsLabelEXT-commandBuffer-01912 ] Object 0: handle = 0x7f524c2966f0, name = bloom_upsampling_pass, type = VK_OBJECT_TYPE_COMMAND_BUFFER; | MessageID = 0x56146426 | vkCmdEndDebugUtilsLabelEXT() called without a corresponding vkCmdBeginDebugUtilsLabelEXT first The Vulkan spec states: There must be an outstanding vkCmdBeginDebugUtilsLabelEXT command prior to the vkCmdEndDebugUtilsLabelEXT on the queue that commandBuffer is submitted to (https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/vkspec.html#VUID-vkCmdEndDebugUtilsLabelEXT-commandBuffer-01912)
2023-05-25T21:58:32.096968Z ERROR wgpu_hal::vulkan::instance:     command buffers: bloom_upsampling_pass
2023-05-25T21:58:32.096978Z ERROR wgpu_hal::vulkan::instance:     objects: (type: COMMAND_BUFFER, hndl: 0x7f524c2966f0, name: bloom_upsampling_pass)

Additional information

I cannot notice anything wrong the actual bloom rendering, it visually looks fine.

@Azorlogh Azorlogh added C-Bug An unexpected or incorrect behavior S-Needs-Triage This issue needs to be labelled labels May 25, 2023
@alice-i-cecile alice-i-cecile added A-Rendering Drawing game state to the screen S-Needs-Investigation This issue requires detective work to figure out what's going wrong and removed S-Needs-Triage This issue needs to be labelled labels May 26, 2023
@JMS55
Copy link
Contributor

JMS55 commented May 26, 2023

Can't reproduce on main

AdapterInfo { name: "Intel(R) UHD Graphics 620 (KBL GT2)", vendor: 32902, device: 22807, device_type: IntegratedGpu, driver: "Intel open-source Mesa driver", driver_info: "Mesa 22.3.7", backend: Vulkan }

SystemInfo { os: "Linux 37 Fedora Linux", kernel: "6.1.18-200.fc37.x86_64", cpu: "Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz", core_count: "4", memory: "7.7 GiB" }

@JMS55
Copy link
Contributor

JMS55 commented May 28, 2023

This might be caused by gfx-rs/wgpu#3809

@tecbeast42
Copy link

I have the same issue, also on Arch linux 6.3.9 with an AMD gpu.

Examples:

  • bloom_2d
  • bloom_3d

have the same behaviour

AdapterInfo { name: "AMD Radeon Graphics", vendor: 4098, device: 5686, device_type: IntegratedGpu, driver: "AMD open-source driver", driver_info: "2023.Q2.3 (LLPC)", backend: Vulkan }

{ os: "Linux rolling Arch Linux", kernel: "6.3.9-arch1-1", cpu: "AMD Ryzen 7 4800H with Radeon Graphics", core_count: "8", memory: "62.2 GiB" }

@tecbeast42
Copy link

Error persist on current dev-main 9309d89

@Kanabenki
Copy link
Contributor

@tecbeast42 It seems the validation layer fix was merged in wgpu 0.17.0. Could you test again on the current main, since it uses 0.17.1, and your test was done when it used 0.16.0 ? I couldn't reproduce both on the current main (8efcbf3) and on 9309d89.

@tecbeast42
Copy link

It seems to be working fine now. 👍

@Kanabenki
Copy link
Contributor

@alice-i-cecile It seems this can be closed then 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Rendering Drawing game state to the screen C-Bug An unexpected or incorrect behavior S-Needs-Investigation This issue requires detective work to figure out what's going wrong
Projects
None yet
Development

No branches or pull requests

5 participants