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

[memory-0.2.1] prevent over-allocation #34

Merged
merged 4 commits into from
Oct 13, 2020
Merged

Conversation

kvark
Copy link
Member

@kvark kvark commented Oct 12, 2020

This is an extract from #31 that makes sense to release as a published version, with improvements.
Specifically, #32 and #33 are addressed here.

Copy link
Member

@cwfitzgerald cwfitzgerald left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nothing catches my eye as obviously incorrect, and the logic seems sound. Has this been tested at all (either here or in #31)

LGTM

@kvark
Copy link
Member Author

kvark commented Oct 13, 2020

This has been tested on DungeonFog, where it addresses the OOM

@kvark
Copy link
Member Author

kvark commented Oct 13, 2020

Thanks for reviewing! ❤️

@kvark kvark merged commit 1faccf9 into gfx-rs:hal-0.6 Oct 13, 2020
@kvark kvark deleted the 0.6-mem branch October 13, 2020 18:55
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

Successfully merging this pull request may close these issues.

2 participants