KhronosGroup / KhronosGroup/Vulkan-ValidationLayers

Reproducible device lost and reproducible DLL crash in toplevel

Open
#3,681 8 comments 0 reactions 0 assignees View on GitHub
Bug
Dominant language
C++
Stars
1k
Forks
504
Avg merge
11h 35m
Merged PRs (30d)
224

Description

**Describe the Issue**
I am using the Vulkan Configurator to validate my test program where I build sample code for various usage techniques with Vulkan.
I have a reproducible device lost when working with shader-based validation and a subpass input.
Another problem is a reproducible crash with an invalid memory access in VkLayer_khronos_validation.dll when resizing my window and remaking the swapchain.

**Valid Usage ID**
N/A

**Environment:**
- OS: Windows 10 x64
- GPU: NVidia GeForce GTX 2070 SUPER OC
- SDK or header version if building from repo: VulkanSDK-1.2.198.1-Installer.exe
- Vulkan Instance Version: 1.2.189
- Options enabled (synchronization, best practices, etc.): (See notes and screenshots in zip file)

**Additional context**
I've taken part in the recent LunarG Vulkan survey and was contacted with a request to file a crash report.
Today I've updated my drivers and the SDK to the most recent versions, made sure that no validation and synchronization validation errors are left, and reproduced these problems.

My sample with code excerpts is at http://hai.dogpixels.net/temp-LunarG/2022-01-16-Hs-Vulkan-Test.zip
Notes.txt in there illustrates how to get into the crash situations.
A visible part of my Vulkan experiments is documented in this retweet chain: https://twitter.com/BestYeen/status/1475964338464768001

Best regards and keep up the awesome work!

Contributor guide

Open the contributing guide

Research direction

Start with Notes.txt and the sample code in the linked archive to reproduce both failures on the reported Windows and Vulkan environment. Trace the validation-layer paths reached during shader-based validation with a subpass input and swapchain recreation; done means both reproductions no longer cause device loss or an invalid memory access.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
computer-graphics, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.