KhronosGroup / KhronosGroup/Vulkan-ValidationLayers

Fix object tracking so invalid handle edge cases are all caught

Open
#10,549 5 comments 1 reaction 1 assignee Claimed by @spencer-lunarg View on GitHub
Bug
Dominant language
C++
Stars
1k
Forks
504
Avg merge
11h 35m
Merged PRs (30d)
224

Description

From https://github.com/KhronosGroup/Vulkan-ValidationLayers/issues/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

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.