Skip to content

Fix object tracking so invalid handle edge cases are all caught #10549

@spencer-lunarg

Description

@spencer-lunarg

From #10519

We have this UNASSIGNED-VkDescriptorImageInfo-BoundResourceFreedMemoryAccess VU which I tried to add to the spec in https://gitlab.khronos.org/vulkan/vulkan/-/merge_requests/5598 but I am now convinced that this is really just missing coverage in object tracker

We need to make sure we detect and give good error messages around these cases instead of trying to manually add each case like

- CreateImage
- BindToMemory
- Free the memory
- Create ImageView with the now broken Image (should be error)

and

- CreateImage
- BindToMemory
- Create ImageView with the good Image
- Destroy Image
- Keep the memory alive
- Use the now invalid ImageView in a function call (should be error)

I want to only focus outside of Command Buffer recording time, but things like VkDescriptorImageInfo clearly seem to be missing these cases

Metadata

Metadata

Assignees

Labels

BugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions