8000 fixes a vulkan validation error , VUID-vkDestroyInstance-instance-00629 by Abhinavpatel00 · Pull Request #45 · zeux/niagara · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

fixes a vulkan validation error , VUID-vkDestroyInstance-instance-00629 #45

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

Merged
merged 1 commit into from
Feb 16, 2025

Conversation

Abhinavpatel00
Copy link
Contributor

well i got the error so i fixed it ,

./niagara list
Enabled Vulkan validation layers (sync validation disabled)
GPU0: Intel(R) UHD Graphics (TGL GT2) (Vulkan 1.3)
ERROR: No compatible GPU found
ERROR: Validation Error: [ VUID-vkDestroyInstance-instance-00629 ] Object 0: handle = 0x62deab6327f0, type = VK_OBJECT_TYPE_INSTANCE; Object 1: handle = 0xfd5b260000000001, type = VK_OBJECT_TYPE_DEBUG_REPORT_CALLBACK_EXT; | MessageID = 0x8b3d8e18 | vkDestroyInstance():  OBJ ERROR : For VkInstance 0x62deab6327f0[], VkDebugReportCallbackEXT 0xfd5b260000000001[] has not been destroyed.
The Vulkan spec states: All child objects created using instance must have been destroyed prior to destroying instance (https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/vkspec.html#VUID-vkDestroyInstance-instance-00629)
niagara: /home/lka/practice/mygames/niagara/src/device.cpp:142: VkBool32 debugReportCallback(VkDebugReportFlagsEXT, VkDebugReportObjectTypeEXT, uint64_t, size_t, int32_t, const char*, const char*, void*): Assertion `!"Validation error encountered!"' failed.

@Abhinavpatel00
Copy link
Contributor Author

somehow it still doesn't work

./niagara list
Enabled Vulkan validation layers (sync validation disabled)
GPU0: Intel(R) UHD Graphics (TGL GT2) (Vulkan 1.3)
ERROR: No compatible GPU found

@zeux
Copy link
Owner
zeux commented Feb 16, 2025

The code was recently switched to require Vulkan 1.4; I’m not sure if Intel has released compatible drivers yet.

@zeux
Copy link
Owner
zeux commented Feb 16, 2025

I'll merge this fix since this is good to apply anyway; if you want to run this using your existing drivers, you can sync to tag vulkan1.3 which is the last version before the 1.4 update.

@zeux zeux merged commit c824ce5 into zeux:master Feb 16, 2025
1 check passed
@Abhinavpatel00
Copy link
Contributor Author
Abhinavpatel00 commented Feb 18, 2025

yeah i tried and i got this

(gdb) run   list
Starting program: /home/lka/practice/mygames/niagara-vulkan1.3/niagara list
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Enabled Vulkan validation layers (sync validation disabled)
[New Thread 0x7ffff2abe6c0 (LWP 19293)]
GPU0: Intel(R) UHD Graphics (TGL GT2)
Selected GPU Intel(R) UHD Graphics (TGL GT2)
[New Thread 0x7ffff6eb06c0 (LWP 19294)]
ERROR: Validation Error: [ VUID-VkShaderModuleCreateInfo-pCode-08740 ] | MessageID = 0x6e224e9 | vkCreateShaderModule():  SPIR-V Capability MeshShadingEXT was declared, but one of the following requirements is required (VK_EXT_mesh_shader).
The Vulkan spec states: If pCode is a pointer to SPIR-V code, and pCode declares any of the capabilities listed in the SPIR-V Environment appendix, one of the corresponding requirements must be satisfied (https://www.khronos.org/registry/vulkan/specs/1.3-extensions/html/vkspec.html#VUID-VkShaderModuleCreateInfo-pCode-08740)
niagara: /home/lka/practice/mygames/niagara-vulkan1.3/src/device.cpp:135: VkBool32 debugReportCallback(VkDebugReportFlagsEXT, VkDebugReportObjectTypeEXT, uint64_t, size_t, int32_t, const char*, const char*, void*): Assertion `!"Validation error encountered!"' failed.

Thread 1 "niagara" received signal SIGABRT, Aborted.
__pthread_kill_implementation (threadid=<optimized out>, 
    signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
44	     return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0;

@zeux
Copy link
Owner
zeux commented Feb 18, 2025

Yeah this is part of why there was a switch to Vulkan 1.4; this specific error is benign (you can just disable validation and it's going to work just fine in practice I believe). This was introduced by the shader loading rework, the last commit before it is probably cd13034

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants
0