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.

Sign up for GitHub

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

Jump to bottom

Loader test CreateInstanceDeviceIntentionalAllocFail fails on AMD #3

Closed
karl-lunarg opened this issue May 14, 2018 · 2 comments
Closed

Loader test CreateInstanceDeviceIntentionalAllocFail fails on AMD #3

karl-lunarg opened this issue May 14, 2018 · 2 comments
Assignees
@lenny-lunarg
Labels
bug Something isn't working
Milestone
P2

Comments

@karl-lunarg
Copy link
Contributor

Issue by krOoze (MIGRATED)
Tuesday Sep 19, 2017 at 17:38 GMT
Originally opened as KhronosGroup/Vulkan-LoaderAndValidationLayers#2078

Running vk_loader_validation_tests I get:

[ RUN ] Allocation.CreateInstanceDeviceIntentionalAllocFail
C:\Dev\_GitHub\Vulkan-LoaderAndValidationLayers\tests\loader_validation_tests.cpp(1454): error: Value of: VK_SUCCESS
Actual: 0
Expected: result
Which is: -3
[ FAILED ] Allocation.CreateInstanceDeviceIntentionalAllocFail (1639 ms)

This is on Windows 10 x64, AMD R9 280X, Radeon Software 17.9.1.
UPDATE: still in 17.11.1.
@karl-lunarg karl-lunarg added this to the P2 milestone May 14, 2018
@karl-lunarg karl-lunarg added bug Something isn't working loader labels May 14, 2018
djdeath pushed a commit to djdeath/Vulkan-Loader that referenced this issue Nov 12, 2018
@llandwerlin-intel
loader: Fix Vk instance given to layer
878bb3f 
The instance give to the layer entry points appears to be an internal
loader structure. While running with RenderDoc, I would hit a crash
where Renderdoc doesn't get the right pointer to find its own private
structures :

 #0  VK_LAYER_RENDERDOC_CaptureGetInstanceProcAddr (instance=0x7fffe4006d00, pName=0x7ffff56dc2bb "vkSetDebugUtilsObjectNameEXT") at /home/djdeath/src/mesa-src/renderdoc/renderdoc/driver/vulkan/vk_layer.cpp:376
 KhronosGroup#1  0x00007ffff56a8dbb in loader_init_device_extension_dispatch_table (dev_table=0x7fffe42ea6a0, gipa=0x7ffff73ca734 <VK_LAYER_RENDERDOC_CaptureGetInstanceProcAddr(VkInstance, char const*)>, gdpa=0x7ffff73c7d70 <VK_LAYER_RENDERDOC_CaptureGetDeviceProcAddr(VkDevice, char const*)>, inst=0x7fffe4006d00,
     dev=0x7ffff3bd8fe0) at /home/djdeath/src/mesa-src/Vulkan-Loader/build/loader/vk_loader_extensions.c:572
 KhronosGroup#2  0x00007ffff56c62cc in vkCreateDevice (physicalDevice=0x7fffe42c31b0, pCreateInfo=0x7ffff1324670, pAllocator=0x0, pDevice=0x7fffe4005c80) at /home/djdeath/src/mesa-src/Vulkan-Loader/loader/trampoline.c:851
 KhronosGroup#3  0x00000000007fc6b0 in ?? ()
@krOoze
Copy link
Contributor

krOoze commented Nov 12, 2018

FYI: still in 18.11.1

@lenny-lunarg
Copy link
Contributor

This test passes on most systems (include the Linux mesa AMD drivers). On top of that, the error happens when counting that every allocation was freed. And since this doesn't happen on any other system, I believe this is a driver issue. As such I'm closing this.

@jbauman42 jbauman42 mentioned this issue Sep 7, 2021
Closed
@phuang phuang mentioned this issue Mar 15, 2022
Closed
@y-novikov y-novikov mentioned this issue Dec 18, 2023
Closed
@y-novikov y-novikov mentioned this issue May 8, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lenny-lunarg lenny-lunarg

Labels
bug Something isn't working
Projects
None yet
Milestone
P2
Development

No branches or pull requests
3 participants
@krOoze @karl-lunarg @lenny-lunarg