Fix state tracker crash on VK_QUEUE_FAMILY_IGNORED - #21
Closed
olehkuznetsov wants to merge 0 commit into
Closed
Conversation
olehkuznetsov
force-pushed
the
fix-capture-p11
branch
11 times, most recently
from
August 5, 2026 13:08
574ec37 to
885e344
Compare
olehkuznetsov
force-pushed
the
fix-capture-p11
branch
from
August 5, 2026 13:10
885e344 to
af7c757
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When reading image/buffer resources during state tracking (e.g. at frame capture start), resources with VK_QUEUE_FAMILY_IGNORED (such as CONCURRENT sharing mode resources) were passing their ignored index down to VulkanResourcesUtil, which subsequently invoked vkGetDeviceQueue with an out of bounds queue constraint (~0U), causing a segmentation fault in the Android Vulkan loader.
This fixes it entirely cleanly in the caller layer by looking up the first valid queue initialized on the device when VK_QUEUE_FAMILY_IGNORED is encountered, hiding this semantic knowledge from the internal utility functions.