Improved handling of DeviceMemory/MemoryBufferPool out of memory conditions to prevent crashes during database paging. #1661
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…e that newly compiled paged databases don't exceed memory limits and cause a crash.
…l over how much device memory can be used by application
…enable control over what raio of available heap memory on device is allocated by the VSG. Added MemoryBufferPools::throwOutOfDeviceMemoryException bool to control whether MemoryBufferPools::reserveMemory(..) should throw an vsg::Exception on failure to allocated memory from a vk/vsg::DeviceMemory
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.