When continuously destroying and recreating a pipeline using one or more specialization constants that have a different value each time, then calling vkQueuePresentKHR, sometimes following exception gets thrown:
Exception thrown at 0x00007FFC77022634 (nvoglv64.dll) in VulkanSpecializationConstantsBugTest.exe: 0xC0000005: Access violation reading location 0x000001D73DA180D8.
In the attached test application this happens when resizing the window for some amount of time (usually within a few seconds on my machine, sometimes instantly). The window size is used as value for the specialization constant. The pipeline is not used and only contains a vertex shader. Note that the unnecessary instructions in the vertex shader simply increase the likelyhood of the exception being thrown for demonstration purposes, but it happens regardless of the amount of code.
I’m using Windows 10 Pro x64, 16 GB RAM, Intel i5-7600, GTX 1080 Ti, driver version 445.75.
Test application download: 39.6 KB file on MEGA