-
Notifications
You must be signed in to change notification settings - Fork 18
Description
When I have a debug build of GPUReshape running with discoverability enabled, my Vulkan application crashes with following callstack:
Crash detected, current frames:
[00007FFC9DA4BDD0] DebugBreak
C:\Windows\System32\KERNELBASE.dll
[00007FFBBA43D92B] Hook_vkGetDeviceProcAddr
D:\Tools\GPU Reshape\23-6-28\artifacts-debug\Bin\MSVC\Debug\GRS.Backends.Vulkan.Layer.dll
[00007FFBBA43D92B] Hook_vkGetDeviceProcAddr
D:\Tools\GPU Reshape\23-6-28\artifacts-debug\Bin\MSVC\Debug\GRS.Backends.Vulkan.Layer.dll
[00007FFBBA43D92B] Hook_vkGetDeviceProcAddr
[00007FFBBA43D92B] Hook_vkGetDeviceProcAddr
[00007FFBBA43D92B] Hook_vkGetDeviceProcAddr
[00007FFC0D63EAF0] vkDestroyDescriptorPool
[00007FFC0D63EAF0] vkDestroyDescriptorPool
[00007FFC0D63EAF0] vkDestroyDescriptorPool
[00007FFC0D63EAF0] vkDestroyDescriptorPool
[00007FFC0D63EAF0] vkDestroyDescriptorPool
[00007FFC0D63EAF0] vkDestroyDescriptorPool
[00007FFC0D63EAF0] vkDestroyDescriptorPool
[00007FFC0D63EAF0] vkDestroyDescriptorPool
[00007FFC0D63EAF0] vkDestroyDescriptorPool
[00007FFC9F792690] BaseThreadInitThunk
[00007FFCA034A9D0] RtlUserThreadStart
Waiting for debugger to attach...
This does not happen with the release build of GPUReshape. Also note, that at this point I have not added the Vulkan application to my workspace nor instrumented anything.
Are there any validation layers enabled in debug mode that are not enabled in release mode?