KhronosGroup / KhronosGroup/Vulkan-Tools
vulkaninfo: No Surface & Window destroy on non-zero return code
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 493
- Forks
- 202
- Avg merge
- 1h 37m
- Merged PRs (30d)
- 4
Description
Hey! As in title and its actually not relevant when built as executable tho I'm leaving raii exiter in following commit
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked commit and inspect the related vulkaninfo cleanup path. Reproduce the non-zero return case and verify that the surface and window are destroyed correctly, including when no surface is available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- computer-graphics, devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100