fix: set M_MMAP_THRESHOLD to prevent memory fragmentation #73
+32
−8
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.
I read some articles about how a default behavior of glibc malloc causes some applications to consume large amounts of RAM until reaching OOM. There's a tunable parameter called
M_MMAP_THRESHOLD
(or theMALLOC_MMAP_THRESHOLD_
environment variable) which defines when an allocation will use mmap instead of sbrk.Small sbrk buffers are stored by malloc in arenas for reuse by the application. mmap buffers are released by the OS instantly on drop. The problem is that the default behavior of malloc is to dynamically increase the threshold if this tunable is not set, which leads to some applications storing lots of randomly-sized gigantic buffers in its arenas, which may never be freed.
This lowered memory usage of cosmic-bg on my system from 96 MB to 25 MB.