FEXCore/Utils: Implements a new atomic segmented bitmap allocator - #5815
Merged
Conversation
Sonicadvance1
force-pushed
the
198
branch
10 times, most recently
from
August 10, 2026 21:27
355ced4 to
b9eca66
Compare
lioncash
reviewed
Aug 11, 2026
lioncash
left a comment
Contributor
There was a problem hiding this comment.
Just two nits, but overall looks good
lioncash
reviewed
Aug 12, 2026
This is tailored towards our needs for our JIT and eventually replacing the linear allocator. Allowing us to reallocate memory for code blocks that have been invalidated, letting us keep a single code buffer around for longer and using less memory overall. In particular, high-invalidation games that ship anti-tamper tend to emit millions of ~128-byte blocks in just a handful of minutes which causes our current linear allocator to consume gigabytes very quickly. This will allow us to more aggressively reuse the allocation space and reduce the memory load in those situations. There's some additional resize tuning that needs some work whence it is in situ which doesn't need to be done now.
lioncash
approved these changes
Aug 12, 2026
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
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.
This is tailored towards our needs for our JIT and eventually replacing
the linear allocator. Allowing us to reallocate memory for code blocks
that have been invalidated, letting us keep a single code buffer around
for longer and using less memory overall.
In particular, high-invalidation games that ship anti-tamper tend to
emit millions of ~128-byte blocks in just a handful of minutes which
causes our current linear allocator to consume gigabytes very quickly.
This will allow us to more aggressively reuse the allocation space and
reduce the memory load in those situations.
There's some additional resize tuning that needs some work whence it is
in situ which doesn't need to be done now.