Code Monkey home page Code Monkey logo

Comments (6)

MarkY-LunarG avatar MarkY-LunarG commented on July 28, 2024

I don't see a segfault, but I do see it failing in vkGetPhysicalDeviceSurfacePreentModesKHR on Fedora Core 28.

With this error:

[gfxrecon] ERROR - API call (vkGetPhysicalDeviceSurfacePresentModesKHR) returned value VK_INCOMPLETE that does not match return value from capture file VK_SUCCESS.

from gfxreconstruct.

dustin-lunarg avatar dustin-lunarg commented on July 28, 2024

I am assuming this is the pNext handle mapping issue, which may produce different results on different drivers.

from gfxreconstruct.

MarkY-LunarG avatar MarkY-LunarG commented on July 28, 2024

I'm wondering the same.

from gfxreconstruct.

MarkY-LunarG avatar MarkY-LunarG commented on July 28, 2024

It looks like what I am seeing is entirely related to the VK_KHR_wayland_surface extension. If I remove only that extension from the list, it works for me. Must be something to do with the handle logic.

(Updated with more info I tracked down)

It appears to be failing on the replay on the vkGetPhysicalDeviceSurfacePresentModesKHR call for the Wayland window surface. So, maybe the Wayland surface isn't properly returned by the tools vkCreateWaylandSurfaceKHR or passed into vkGetPhysicalDeviceSurfacePresentModesKHR.

from gfxreconstruct.

MarkY-LunarG avatar MarkY-LunarG commented on July 28, 2024

Ok, so my problem is that VulkanInfo is recording surface presentation information under Wayland during the recording. [Actually it records the info for Xlib, XCB and Wayland]. When it records the Wayland information, it only gets 2 surface present modes. So the first call to vkGetPhysicalDeviceSurfacePresentModesKHR returns 2, then VulkanInfo creates an array of 2 and fills in the contents.

On playback, the replay tool is running each of those surface queries through it's XCB surface which has more than 2 present modes. So when vkGetPhysicalDeviceSurfacePresentModesKHR is called the first time, it returns 4. The second time vkGetPhysicalDeviceSurfacePresentModesKHR with an array of size 2, vkGetPhysicalDeviceSurfacePresentModesKHR returns VK_INCOMPLETE.

from gfxreconstruct.

dustin-lunarg avatar dustin-lunarg commented on July 28, 2024

The crash is happening because replay does not set the sType and pNext values for the VkQueueFamilyProperties2 structures that are used when calling GetPhysicalDeviceQueueFamilyProperties2.

Should be fixed by #196

from gfxreconstruct.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.