Skip to content

Fix Vulkan memoryType selection for QNX Screen buffer imports - #208

Merged
aaron-ruby merged 1 commit into
google:mainfrom
aaron-ruby:qnx-memoryType-fix
Oct 14, 2026
Merged

aaron-ruby merged 1 commit into
google:mainfrom
aaron-ruby:qnx-memoryType-fix

Conversation

@aaron-ruby

Copy link
Copy Markdown
Collaborator

... and fall-back to attempting selection using only Screen buffer memoryTypeBits when there is no combined type available.

... and fall-back to attempting selection using only Screen buffer
memoryTypeBits when there is no combined type available.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request modifies the external memory allocation logic in vk_common_operations.cpp to fall back to the screen buffer's memory type bits when no common memory type is found with the VkImage, rather than returning an error. Review feedback highlights that this fallback violates Vulkan specification VUID-vkBindImageMemory-memory-01047, which can lead to failures or undefined behavior on strict Vulkan drivers. Additionally, a minor grammatical typo in the warning message was noted.

Comment thread host/vulkan/vk_common_operations.cpp
Comment thread host/vulkan/vk_common_operations.cpp
@aaron-ruby
aaron-ruby added this pull request to the merge queue Oct 14, 2026
Merged via the queue into google:main with commit 5960b81 Oct 14, 2026
19 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants