Closed bl4ckb0ne closed 1 year ago
This is crashing on a call to one of the drivers vkEnumerateDeviceExtensionProperties
. I have a strong suspicion that this is from the Intel driver but have nothing to confirm it.
Running renderdoc locally does not produce any crash of the sorts for me.
Can you manually select each driver one by one to see if only one of them is provoking a crash? You can use the VK_LOADER_DRIVERS_SELECT
environment variable to do so.
For instance, based on your log file these would be the 4 values to set the env-var to:
VK_LOADER_DRIVERS_SELECT=lvp_icd.x86_64.json
VK_LOADER_DRIVERS_SELECT=intel_hasvk_icd.x86_64.json
VK_LOADER_DRIVERS_SELECT=intel_icd.x86_64.json
VK_LOADER_DRIVERS_SELECT=radeon_icd.x86_64.json
Another possible source of error is the fact that there are a few implicit layers on your system while the stack trace shows no implicit layers intercepting the vkEnumeratePhysicalDevices calls. VkLayer_MESA_device_select is a possible candidate for issues, I would do a similar check with VK_LOADER_LAYERS_DISABLE=VkLayer_MESA_device_select
to confirm that isn't the issue.
Seems to be working with VK_LOADER_DRIVERS_SELECT=radeon_icd.x86_64.json
and VK_LOADER_DRIVERS_SELECT=lvp_icd.x86_64.json
, I'll report the issue to Mesa
Describe the bug I'm encountering a SIGSEGV when calling
vkEnumeratePhysicalDevices
in renderdoc 1.25 1Environment (please complete the following information):
To Reproduce Steps to reproduce the behavior:
qrenderdoc
VK_LOADER_DEBUG output
vk_loader_debug.log
Stacktrace