[Bug 101081] Error when resizing windows while running Vulkan Examples from SDK

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Wed May 17 22:09:06 UTC 2017


            Bug ID: 101081
           Summary: Error when resizing windows while running Vulkan
                    Examples from SDK
           Product: Mesa
           Version: 17.0
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: major
          Priority: medium
         Component: Drivers/Vulkan/intel
          Assignee: intel-3d-bugs at lists.freedesktop.org
          Reporter: johnz at lunarg.com
        QA Contact: intel-3d-bugs at lists.freedesktop.org
                CC: jason at jlekstrand.net

Running the cube example out of the Vulkan SDK and resizing the window will
cause a black window. Nothing gets drawn after resizing and an some fence
warnings get thrown to console.

This problem has been reproduced with Mesa 17.0.4, 17.0.5, and 17.0.6 on Ubuntu
16.04 and Fedora 25.

Steps to reproduce:
Build the examples from LunarG's Vulkan SDK (Download the SDK
[https://vulkan.lunarg.com/sdk/home]; follow the getting started guide
[https://vulkan.lunarg.com/doc/sdk/] if

Run the cube example and resize the window. The area will become black as
nothing gets drawn after resizing. If you run with the "--validate" option
after setting your environmental variables the following fence warning is sent
to the console:
$ ./cube --validate
WARNING: [ParameterValidation] Code 9 : vkAcquireNextImageKHR: returned
VK_ERROR_OUT_OF_DATE_KHR, indicating that a surface has changed in such a way
that it is no longer compatible with the swapchain
WARNING: [MEM] Code 10 : vkWaitForFences called for fence 0x5 which has not
been submitted on a Queue or during acquire next image.

You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20170517/29f6dcee/attachment.html>

More information about the intel-3d-bugs mailing list