Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vulkan allocator should respect the maxMemoryAllocationCount limit #125

Open
i509VCB opened this issue Aug 26, 2022 · 0 comments
Open

Vulkan allocator should respect the maxMemoryAllocationCount limit #125

i509VCB opened this issue Aug 26, 2022 · 0 comments

Comments

@i509VCB
Copy link

i509VCB commented Aug 26, 2022

The specification states the following inside the documentation of vkAllocateMemory:

For historical reasons, if maxMemoryAllocationCount is exceeded, some implementations may return VK_ERROR_TOO_MANY_OBJECTS. Exceeding this limit will result in undefined behavior, and an application should not rely on the use of the returned error code in order to identify when the limit is reached.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant