You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@elfarouk wants statically-allocated bitmaps to avoid memory fragmentation. Not easy with the current implementation. If we implement bitmaps that are already preallocated #255 and we say that applications using higher bits are buggy, we could extend to statically allocated bitmaps.
The text was updated successfully, but these errors were encountered:
AIUI it's just a performance question. We could let the application just configure the default bitmap size, and use that as default allocation for bitmaps. If the application doesn't go beyond it, there won't be reallocations, if it does, there will be reallocations, but that will only have performance consequences.
@elfarouk wants statically-allocated bitmaps to avoid memory fragmentation. Not easy with the current implementation. If we implement bitmaps that are already preallocated #255 and we say that applications using higher bits are buggy, we could extend to statically allocated bitmaps.
The text was updated successfully, but these errors were encountered: