VkBindImageMemory With NULL VkDeviceMemory Handle Does Not ...

Skip to content Dismiss alert {{ message }} / Vulkan-ValidationLayers Public
  • Notifications You must be signed in to change notification settings
  • Fork 470
  • Star 973
  • Code
  • Issues 290
  • Pull requests 6
  • Actions
  • Projects
  • Security
  • Insights
Additional navigation options vkBindImageMemory with NULL VkDeviceMemory handle does not trigger a validation warning #143New issueNew issueClosedClosedvkBindImageMemory with NULL VkDeviceMemory handle does not trigger a validation warning#143Assignees lenny-lunargMilestonesdk-1.1.108.0@nsubtil

Description

@nsubtilnsubtilopened on May 27, 2018

Recently ran into an app bug where a NULL memory handle was being passed in to vkBindImageMemory. This did not trigger validation errors, even though the spec language seems to suggest it should.

Comments around ValidateSetMemBinding seem to suggest that this should cause a warning, but I couldn't find the actual warning anywhere --- it looks like if mem == VK_NULL_HANDLE the function ends up doing nothing. Maybe we're just missing the corresponding log_msg call for that case?

Metadata

Metadata

Assignees

  • @lenny-lunarglenny-lunarg

Labels

No labelsNo labels

Type

No type

Projects

No projects

Milestone

  • sdk-1.1.108.0

Relationships

None yet

Development

No branches or pull requests

Issue actions

You can’t perform that action at this time.

Từ khóa » Vulkan-1.1.108.0-installer