[Vulkan] Workaround for zero size allocation #7691
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It seems we get segfault from Vulkan if a request to allocate 0 size is made. Returning nullptr in such case works for other backend, but VK seems to have issues. This workaround was confirmed to be effective.
Running NMS tests in
test_any.py
serves as the test case. Without this it would segfault.@tmoreau89 @mbrookhart @tqchen