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

Commands are dropped from the trace for subsequent calls to VkCreateInstance #1793

Closed

AWoloszyn opened this issue Apr 12, 2018 · 1 comment

Assignees

Contributor

AWoloszyn commented Apr 12, 2018

In a call to VkCreateInstance we unset the VkGraphicsSpy layer.

If we do this, and an application creates a second instance, the layer will not be loaded. This means any further Vulkan commands will be ignored.

AWoloszyn assigned AWoloszyn and Qining and unassigned AWoloszyn

Contributor

Qining commented Apr 13, 2018

Wow, so we actually have a case with multiple instance?

Qining mentioned this issue

Vulkan on Android: Keep VkGraphicsSpy layer around after VkCreateInstance #1796

Merged

Qining closed this as completed in #1796

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment